From 18be2fb9df3097bbe54c90a420b976dccace4279 Mon Sep 17 00:00:00 2001 From: Valerio Setti Date: Fri, 26 Jan 2024 15:07:02 +0100 Subject: [PATCH] driver-only-builds: improve a sentence in the HMAC section Signed-off-by: Valerio Setti --- docs/driver-only-builds.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/driver-only-builds.md b/docs/driver-only-builds.md index e4c30bd33..4095d8ee7 100644 --- a/docs/driver-only-builds.md +++ b/docs/driver-only-builds.md @@ -118,7 +118,9 @@ HMAC by enabling and accelerating: In such a build it is possible to disable legacy HMAC support by disabling `MBEDTLS_MD_C` and still getting crypto operations, X.509 and TLS to work as usual. Exceptions are: -- [Hashes](#hashes) are obviously valid here for the accelerated algorithms. +- As mentioned in [Hashes](#hashes) direct calls to legacy lo-level hash APIs + (`mbedtls_sha256()` etc.) will not be possible for the legacy modules that + are disabled. - Legacy HMAC support (`mbedtls_md_hmac_xxx()`) won't be possible. - `MBEDTLS_PKCS[5|7]_C`, `MBEDTLS_HMAC_DRBG_C` and `MBEDTLS_HKDF_C` since they depend on the legacy implementation of HMAC.