Gilles Peskine 35f057330f Keep track of PSA keys used interally ...

When PSA uses CTR_DRBG for its random generator and CTR_DRBG uses PSA for
AES, as currently implemented, there is one volatile key in permanent use
for the CTR_DRBG instance. Account for that in tests that want to know
exactly how many volatile keys are in use, or how many volatile keys can be
created.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>

2024-08-07 12:39:05 +02:00

..

core

Fix overlap between volatile keys and built-in keys

2024-08-07 12:39:05 +02:00

drivers

Reorder blocks to avoid double negations

2024-08-07 12:39:05 +02:00

include

Add a test for the built-in key range

2024-08-07 12:39:05 +02:00

programs

Add programs directory in tf-psa-crypto directory

2024-07-19 10:07:27 +02:00

tests

Keep track of PSA keys used interally

2024-08-07 12:39:05 +02:00

.gitignore

Adapt libraries installation

2024-06-13 09:02:30 +02:00

CMakeLists.txt

Adjust build systems

2024-07-10 08:07:38 +02:00