yuzu-emu/mbedtls
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

driver-only-builds: improve a sentence in the HMAC section

Browse source 
Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>
This commit is contained in:
Valerio Setti 2024-01-26 15:07:02 +01:00
parent 89d8a12e9c
commit 18be2fb9df
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/driver-only-builds.md
View file

@ -118,7 +118,9 @@ HMAC by enabling and accelerating:
In such a build it is possible to disable legacy HMAC support by disabling 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 `MBEDTLS_MD_C` and still getting crypto operations, X.509 and TLS to work as
usual. Exceptions are: 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. - 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 - `MBEDTLS_PKCS[5|7]_C`, `MBEDTLS_HMAC_DRBG_C` and `MBEDTLS_HKDF_C` since they
depend on the legacy implementation of HMAC. depend on the legacy implementation of HMAC.