Gilles Peskine 91773db331 Add a test for the built-in key range
Restricting the built-in key range would be an API break since applications
can hard-code a built-in key value and expect that it won't clash with
anything else. Make it harder to accidentally break the API.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2024-08-07 11:17:32 +02:00
..
crypto_builtin_composites.h Update headers 2023-11-03 12:54:54 +00:00
crypto_builtin_primitives.h Update headers 2023-11-03 12:54:54 +00:00
crypto_compat.h Update headers 2023-11-03 12:54:54 +00:00
crypto_config.h Update headers 2023-11-03 12:54:54 +00:00
crypto_driver_common.h Update headers 2023-11-03 12:54:54 +00:00
crypto_driver_contexts_composites.h Update headers 2023-11-03 12:54:54 +00:00
crypto_driver_contexts_primitives.h Update headers 2023-11-03 12:54:54 +00:00
crypto_extra.h Add a test for the built-in key range 2024-08-07 11:17:32 +02:00
crypto_platform.h Update headers 2023-11-03 12:54:54 +00:00
crypto_se_driver.h Update headers 2023-11-03 12:54:54 +00:00
crypto_sizes.h Update headers 2023-11-03 12:54:54 +00:00
crypto_struct.h Update headers 2023-11-03 12:54:54 +00:00
crypto_types.h Update headers 2023-11-03 12:54:54 +00:00
crypto_values.h Fix copypasta 2024-02-15 15:32:47 +01:00
crypto.h Prevent mbedtls_psa_register_se_key with volatile keys 2024-08-07 11:17:32 +02:00