12 * \note This file may not be included directly. Applications must
13 * include psa/crypto.h.
15 * This file contains platform-dependent type definitions.
17 * In implementations with isolation between the application and the
18 * cryptography module, implementers should take care to ensure that
19 * the definitions that are exposed to applications match what the
20 * module implements.
26/* PSA requires several types which C99 provides in stdint.h. */
29/* Integral type representing a key handle. */
30typedef uint16_t psa_key_handle_t;
32/* This implementation distinguishes *application key identifiers*, which
33 * are the key identifiers specified by the application, from
34 * *key file identifiers*, which are the key identifiers that the library
35 * sees internally. The two types can be different if there is a remote
36 * call layer between the application and the library which supports
37 * multiple client applications that do not have access to each others'
38 * keys. The point of having different types is that the key file
39 * identifier may encode not only the key identifier specified by the
40 * application, but also the the identity of the application.
42 * Note that this is an internal concept of the library and the remote
43 * call layer. The application itself never sees anything other than
44 * #psa_app_key_id_t with its standard definition.
47/* The application key identifier is always what the application sees as
48 * #psa_key_id_t. */
49typedef uint32_t psa_app_key_id_t;
51#endif /* PSA_CRYPTO_PLATFORM_H */
Important Information for this Arm website
By continuing to use our site, you consent to our cookies.
If you are not happy with the use of these cookies, please review our
to learn how they can be disabled.
By disabling cookies, some features of the site will not work.