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
[nrf toup] [Crypto] Fix the wrong handling PSA pending keypair.
The pending keypair was handled in a wrong way in the PSA PAL.
This keypair should be saved to ITS as volatile persistence, then
all operations should be done using this instance, and it must be
saved to persistent storage in the CommitOpKeypairForFabric
function.
Previously, the same KeyId was used both to active
and pending keypairs, and when a failsafe occurs, then this key
has been removed and there is no key for the fabric anymore.
Main changes:
- PersistentP256Keypair::Generate generates a pending
keypair as volatile with additional usage flag PSA_KEY_USAGE_COPY.
- In the CommitOpKeypairForFabric function the pending keypair
is copied to persistent location, and the keyId for fabric is
replaced.
Signed-off-by: Arkadiusz Balys <[email protected]>
0 commit comments