psa_open_key() is only used within mbedTLS.
 
Symbols
loading...
Files
loading...
SummarySyntaxArgumentsReferences

Return value

#PSA_SUCCESS Success. The application can now use the value of `*handle` to access the key. #PSA_ERROR_INSUFFICIENT_MEMORY The implementation does not have sufficient resources to open the key. This can be due to reaching an implementation limit on the number of open keys, the number of open key handles, or available memory. #PSA_ERROR_DOES_NOT_EXIST There is no persistent key with key identifier \p key. #PSA_ERROR_INVALID_ARGUMENT \p key is not a valid persistent key identifier. #PSA_ERROR_NOT_PERMITTED The specified key exists, but the application does not have the permission to access it. Note that this specification does not define any way to create such a key, but it may be possible through implementation-specific means. #PSA_ERROR_COMMUNICATION_FAILURE \emptydescription #PSA_ERROR_CORRUPTION_DETECTED \emptydescription #PSA_ERROR_STORAGE_FAILURE \emptydescription #PSA_ERROR_DATA_INVALID \emptydescription #PSA_ERROR_DATA_CORRUPT \emptydescription #PSA_ERROR_BAD_STATE The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

Notes

This API is not part of the PSA Cryptography API Release 1.0.0 specification. It was defined in the 1.0 Beta 3 version of the specification but was removed in the 1.0.0 released version. This API is kept for the time being to not break applications relying on it. It is not deprecated yet but will be in the near future. Applications that rely on opening a key multiple times will not be portable to implementations that only permit a single key handle to be opened. See also :ref:\`key-handles\`.

References

from examples