mirror of
https://github.com/yuzu-emu/mbedtls.git
synced 2024-12-27 02:15:34 +00:00
80eaa93b59
The compilation guards in key_management.c are now accelerator compilation guards (MBEDTLS_PSA_ACCEL_KEY_TYPE_xyz). As a consequence when running the PSA driver wrapper tests as part of test_psa_crypto_config_basic and test_psa_crypto_drivers all.sh components all key management cryptographic operations were handled by the software builtin fallback, and not by the test driver as intended in the first place. This commits fixes this issue by: . declaring an accelerator for ECC key pairs in test_psa_crypto_config_basic. . declaring an accelerator for both ECC and RSA key pairs in test_psa_crypto_drivers. It is possible to declare an accelerator for both ECC and RSA key pairs in test_psa_crypto_drivers and not in test_psa_crypto_config_basic because in the case of test_psa_crypto_drivers the new PSA configuration is not activated. That way, the builtin fallback software implementation is present to supply the transparent test driver when some support is missing in it (mainly RSA key generation). Note that the declaration of accelerators does much more than just "fixing" the execution flow of driver wrapper tests, it makes all import and public key export cryptographic operations in all unit tests being handled by the transparent test driver (provided that it supports the key type). One test case related to key generation is partially disabled. This will be fixed with the rework of psa_generate_key along the lines described in psa-crypto-implementation-structure.md. Signed-off-by: Ronald Cron <ronald.cron@arm.com> |
||
---|---|---|
.. | ||
.jenkins | ||
configs | ||
data_files | ||
docker/bionic | ||
git-scripts | ||
include/test | ||
scripts | ||
src | ||
suites | ||
.gitignore | ||
CMakeLists.txt | ||
compat-in-docker.sh | ||
compat.sh | ||
context-info.sh | ||
Descriptions.txt | ||
make-in-docker.sh | ||
Makefile | ||
ssl-opt-in-docker.sh | ||
ssl-opt.sh |