lib/mbedtls
1
0
Fork 0
mirror of https://github.com/Mbed-TLS/mbedtls.git synced 2025-07-28 00:21:48 +03:00
Code Activity

Introduce MBEDTLS_OR_PSA_WANT_xxx helper macros

Browse Source 
Currently just replacing existing uses, but the real point of having
these conditions as a single macro is that we'll be able to use them in
tests case dependencies, see next commit.

Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
This commit is contained in:
Manuel Pégourié-Gonnard
2022-07-15 11:05:05 +02:00
parent 3637c516a4
commit f88b1b5375
4 changed files with 76 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/architecture/psa-migration/strategy.md
View File

@ -311,7 +311,7 @@ readability or testability.
**Strategy for step 3:**
There are currently two (competing) ways for crypto-using code to check if a
There are currently two (complementary) ways for crypto-using code to check if a
particular algorithm is supported: using `MBEDTLS_xxx` macros, and using
`PSA_WANT_xxx` macros. For example, PSA-based code that want to use SHA-256
will check for `PSA_WANT_ALG_SHA_256`, while legacy-based code that wants to
@ -331,7 +331,7 @@ information tables that are not tied to a particular crypto API, and may be
used by functions that are either purely PSA-based, purely legacy-based, or
hybrid governed by `MBEDTL_USE_PSA_CRYPTO` should use `MBEDTLS_xxx ||
PSA_WANT_xxx` - for example, `oid_md_alg` from `oid.c`, used by both X.509 and
RSA.
RSA. A new family of macros `MBEDTLS_OR_PSA_WANT_xxx` is defined for this.
To sum up, there are 4 categories:
@ -340,7 +340,7 @@ To sum up, there are 4 categories:
- hybrid code governed by `MBEDTLS_USE_PSA_CRYPTO` can use
`MBEDTLS_USE_PSA_WANT_xxx` to express dependencies in common parts;
- data and crypto-agnostic helpers that can be used by code from at least two
of the above categories should depend on `MBEDTLS_xxx || PSA_WANT_xxx`.
of the above categories should depend on `MBEDTLS_OR_PSA_WANT_xxx`.
Migrating away from the legacy API