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

Fix typos / improve syntax

Browse source 
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
This commit is contained in:
Manuel Pégourié-Gonnard 2024-01-10 09:43:06 +01:00
parent 60c9eee267
commit 0f45a1aec5
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
ChangeLog.d/driver-only-cipher.txt
View file

@ -2,7 +2,7 @@ Features
* If a cipher or AEAD mechanism has a PSA driver, you can now build the * If a cipher or AEAD mechanism has a PSA driver, you can now build the
library without the corresponding built-in implementation. Generally library without the corresponding built-in implementation. Generally
speaking that requires both the key type and algorithm to be accelerated speaking that requires both the key type and algorithm to be accelerated
or they'll both be built in. However for CCM and GCM the built-in or they'll both be built in. However, for CCM and GCM the built-in
implementation is able to take advantage of a driver that only implementation is able to take advantage of a driver that only
accelerates the key type (that is, the block cipher primitive). See accelerates the key type (that is, the block cipher primitive). See
docs/driver-only-builds.md for full details and current limitations. docs/driver-only-builds.md for full details and current limitations.

2
ChangeLog.d/no-cipher.txt
View file

@ -1,7 +1,7 @@
Features Features
* Fewer modules depend on MBEDTLS_CIPHER_C, making it possible to save code * Fewer modules depend on MBEDTLS_CIPHER_C, making it possible to save code
size by disabling it in more circumstances. In particular, the CCM and size by disabling it in more circumstances. In particular, the CCM and
GCM modules no longer depends on MBEDTLS_CIPHER_C. Also, GCM modules no longer depend on MBEDTLS_CIPHER_C. Also,
MBEDTLS_PSA_CRYPTO can now be enabled without MBEDTLS_CIPHER_C if all MBEDTLS_PSA_CRYPTO can now be enabled without MBEDTLS_CIPHER_C if all
unauthenticated (non-AEAD) ciphers are disabled, or if they're all unauthenticated (non-AEAD) ciphers are disabled, or if they're all
fully provided by drivers. See docs/driver-only-builds.md for full fully provided by drivers. See docs/driver-only-builds.md for full

2
docs/architecture/psa-migration/md-cipher-dispatch.md
View file

@ -609,7 +609,7 @@ int psa_can_do_cipher(psa_key_type_t key_type, psa_algorithm_t cipher_alg);
The job of this private function is to return 1 if `hash_alg` can be performed through PSA now, and 0 otherwise. It is only defined on algorithms that are enabled via PSA. As a starting point, return 1 if PSA crypto's driver subsystem has been initialized. The job of this private function is to return 1 if `hash_alg` can be performed through PSA now, and 0 otherwise. It is only defined on algorithms that are enabled via PSA. As a starting point, return 1 if PSA crypto's driver subsystem has been initialized.
Each function in the module needs to know whether to dispatch via PSA or legacy. All function with just consult the context's `engine` field, except `setup()` which will set it according to the key type and the return value of `psa_can_do_cipher()` as discussed above. Each function in the module needs to know whether to dispatch via PSA or legacy. All functions consult the context's `engine` field, except `setup()` which will set it according to the key type and the return value of `psa_can_do_cipher()` as discussed above.
Note that this assumes that an operation that has been started via PSA can be completed. This implies that `mbedtls_psa_crypto_free` must not be called while an operation using PSA is in progress. Note that this assumes that an operation that has been started via PSA can be completed. This implies that `mbedtls_psa_crypto_free` must not be called while an operation using PSA is in progress.