Skip to content

Mbed OS doesn't use latest PSA Crypto API when TF-M is used #13025

@Patater

Description

@Patater

Description of defect

Mbed OS doesn't use latest PSA Crypto API when TF-M is used.

This can by fixed by updating the verion of TF-M that Mbed OS uses to a version of TF-M that has feature parity with the Mbed PSA implementation (which gets pulled in via Mbed TLS), when such a version of TF-M becomes available. TF-M upgrading to get its PSA Crypto implementation from the same version of Mbed TLS that Mbed OS uses will provide such a version of TF-M.

It broke after #12955 was merged

See below

Target(s) affected by this defect ?

All targets using TF-M for their PSA implementation: including PSoC 64 and Musca targets.

Toolchain(s) (name and version) displaying this defect ?

All

What version of Mbed-os are you using (tag or sha) ?

847807e

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

mbed-cli latest
TF-M 1.0

How is this defect reproduced ?

Attempt to build using PSA Crypto API 1.0 functions that don't yet exist in TF-M's PSA implementation, but do exist in Mbed's PSA Crypto implementation.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions