mbedtls/docs/architecture
Janos Follath 0385c2815c Tighten thread safety requirements
We shouldn't violate the requirement that the key identifier can be
reused. In practice, a key manager may destroy a key that's in use by
another process, and the privileged world containing the key manager and
the crypto service should not be perturbed by an unprivileged process.

With respect to blocking, again, a key manager should not be blocked
indefinitely by an unprivileged application.

These are desirable properties even in the short term.

Signed-off-by: Janos Follath <janos.follath@arm.com>
2023-08-30 16:44:04 +01:00
..
psa-migration test: use only rev-parse for getting the current branch 2023-07-31 16:47:07 +02:00
testing Merge pull request #7136 from yanrayw/5692-record-compatsh-test-cases 2023-07-10 12:08:32 +01:00
alternative-implementations.md Additional updates to docs links 2022-10-12 16:47:08 +01:00
Makefile List all markdown files in makefile 2022-06-09 17:36:36 +02:00
mbed-crypto-storage-specification.md Minor adjustments after review. 2023-05-12 15:01:59 +01:00
psa-crypto-implementation-structure.md Merge pull request #5904 from gilles-peskine-arm/psa-doc-implementing-new-mechanism 2023-05-16 14:04:15 +02:00
psa-storage-resilience.md More about whether to have the driver key id in the transaction list 2023-06-13 21:11:43 +02:00
psa-thread-safety.md Tighten thread safety requirements 2023-08-30 16:44:04 +01:00
tls13-support.md Update TLS 1.3 documentation and add change log 2023-04-06 10:26:18 +02:00