You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently using Mbed Crypto 1.1.0 which exposed an old version of PSA Crypto API.
After the interface work is done, we should update the version of mbed we pull to 2.0.0 and modify the way we create and handle keys (where necessary).
Changes that will probably be needed:
Updating the way Mbed Provider handles key creation (as per the new PSA spec)
Updating the way we deal with key lifetimes (deciding how this will be handled is WIP)
Adding permit_copy as a flag for key attributes
If providers will be forced to only support one key lifetime, a new issue shall be raised.
The text was updated successfully, but these errors were encountered:
Most of the functions for populating key attributes structures are defined as static inline. So we either have to populate things by hand or write our own FFI wrappers.
We're currently using Mbed Crypto 1.1.0 which exposed an old version of PSA Crypto API.
After the interface work is done, we should update the version of mbed we pull to 2.0.0 and modify the way we create and handle keys (where necessary).
Changes that will probably be needed:
permit_copy
as a flag for key attributesIf providers will be forced to only support one key lifetime, a new issue shall be raised.
The text was updated successfully, but these errors were encountered: