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

Update testing.md

Browse source 
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
This commit is contained in:
Manuel Pégourié-Gonnard 2022-04-20 12:50:59 +02:00 committed by Manuel Pégourié-Gonnard
parent 2ffb93a83b
commit b8a6c2320e
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/architecture/psa-migration/testing.md
View file

@ -21,11 +21,11 @@ they should be when `MBEDTLS_USE_PSA_CRYPTO` is enabled.
However, when it comes to TLS, we also have the option of using debug messages However, when it comes to TLS, we also have the option of using debug messages
to confirm which code path is taken. This is generally unnecessary, except when to confirm which code path is taken. This is generally unnecessary, except when
a decision is made at run-time about whether to use the PSA or legacy code a decision is made at run-time about whether to use the PSA or legacy code
path. For example, for record protection, currently some ciphers are supported path. (For example, for record protection, previously (until 3.1), some ciphers were supported
via PSA while some others aren't, with a run-time fallback. In this case, it's via PSA while some others weren't, with a run-time fallback. In this case, it's
good to have a debug message checked by the test case to confirm that the good to have a debug message checked by the test case to confirm that the
right decision was made at run-time, i. e. that we didn't use the fallback for right decision was made at run-time, i. e. that we didn't use the fallback for
ciphers that are supposed to be supported. ciphers that are supposed to be supported.)
New APIs meant for application use New APIs meant for application use
@ -54,9 +54,8 @@ In that case, we want:
(We should have the same server-side.) (We should have the same server-side.)
- in `test_suite_x509write` we have a new test function - in `test_suite_x509write` we have a new test function
`x509_csr_check_opaque()` checking integration of the new API with the `x509_csr_check_opaque()` checking integration of the new API with the
existing `mbedtls_x509write_csr_set_key()`. existing `mbedtls_x509write_csr_set_key()`. (And also
(We should have something similar for `mbedtls_x509write_crt_set_issuer_key()` since #5710.)
`mbedtls_x509write_crt_set_issuer_key()`.)
For some APIs, for example with `mbedtls_ssl_conf_psk_opaque()`, testing in For some APIs, for example with `mbedtls_ssl_conf_psk_opaque()`, testing in
`test_suite_ssl` was historically not possible, so we only have testing in `test_suite_ssl` was historically not possible, so we only have testing in
@ -65,8 +64,9 @@ For some APIs, for example with `mbedtls_ssl_conf_psk_opaque()`, testing in
New APIs meant for internal use New APIs meant for internal use
------------------------------- -------------------------------
For example, `mbedtls_cipher_setup_psa()` is meant to be used by the TLS For example, `mbedtls_cipher_setup_psa()` (no longer used, soon to be
layer, but probably not directly by applications. deprecated - #5261) was meant to be used by the TLS layer, but probably not
directly by applications.
In that case, we want: In that case, we want: