|
| | API version |
| |
| | Library initialization |
| |
| | Key management |
| |
| | Key import and export |
| |
| | Message digests |
| |
| | Message authentication codes |
| |
| | Symmetric ciphers |
| |
| | Authenticated encryption with associated data (AEAD) |
| |
| | Asymmetric cryptography |
| |
| | Key derivation and pseudorandom generation |
| |
| | Random generation |
| |
| | Hardware-Accelerated Message Digests |
| | Generation and authentication of Message Digests (aka hashes) must be done in parts using the following sequence:
|
| |
| | Hardware-Accelerated Message Authentication Code |
| | Generation and authentication of Message Authentication Codes (MACs) using cryptographic accelerators can be done either as a single function call (via the psa_drv_accel_mac_generate_t or psa_drv_accel_mac_verify_t functions), or in parts using the following sequence:
|
| |
| | Hardware-Accelerated Block Ciphers |
| | Encryption and Decryption using hardware-acceleration in block modes other than ECB must be done in multiple parts, using the following flow:
|
| |
| | Hardware-Accelerated Authenticated Encryption with Additional Data |
| | Hardware-accelerated Authenticated Encryption with Additional Data (AEAD) operations must be done in one function call.
|
| |
| | Hardware-Accelerated Asymmetric Cryptography |
| | Since the amount of data that can (or should) be encrypted or signed using asymmetric keys is limited by the key size, hardware-accelerated asymmetric key operations must be done in single function calls.
|
| |
| | Entropy Generation |
| |
| | TLS helper functions |
| |
| | Secure element driver initialization |
| |
| | Secure Element Message Authentication Codes |
| | Generation and authentication of Message Authentication Codes (MACs) using a secure element can be done either as a single function call (via the psa_drv_se_mac_generate_t or psa_drv_se_mac_verify_t functions), or in parts using the following sequence:
|
| |
| | Secure Element Symmetric Ciphers |
| | Encryption and Decryption using secure element keys in block modes other than ECB must be done in multiple parts, using the following flow:
|
| |
| | Secure Element Asymmetric Cryptography |
| | Since the amount of data that can (or should) be encrypted or signed using asymmetric keys is limited by the key size, asymmetric key operations using keys in a secure element must be done in single function calls.
|
| |
| | Secure Element Authenticated Encryption with Additional Data |
| | Authenticated Encryption with Additional Data (AEAD) operations with secure elements must be done in one function call.
|
| |
| | Secure Element Key Management |
| | Currently, key management is limited to importing keys in the clear, destroying keys, and exporting keys in the clear.
|
| |
| | Secure Element Key Derivation and Agreement |
| | Key derivation is the process of generating new key material using an existing key and additional parameters, iterating through a basic cryptographic function, such as a hash.
|
| |
| | Secure element driver registration |
| |
| | Error codes |
| |
| | Key and algorithm types |
| |
| | Key lifetimes |
| |
| | Key policies |
| |
| | Key derivation |
| |
| | PSA-Attestation |
| |
| | Key attributes |
| |