test_depends_py_cipher_id_psa: based on full config, one enabled cipher at a time among AES, ARIA, CAMELLIA, CHACHA20, CHACHAPOLY, DES
test_depends_py_cipher_chaining_psa: based on full config, one among CBC, CFB, CTR, OFB, XTS
test_depends_py_cipher_padding_psa: not relevant in psa-crypto
test_depends_py_curves_psa: based on full config, only one elliptic curve
test_depends_py_hashes_psa: based on full config, all but one hash, just SHA256, just SHA512
test_depends_py_kex_psa: not relevant in psa-crypto
test_depends_py_pkalgs_psa: based on full config, !MBEDTLS_ECDSA_C, !MBEDTLS_ECP_C (not relevant in psa-crypto) !MBEDTLS_PKCS1_V15 !MBEDTLS_PKCS1_V21 !MBEDTLS_RSA_C !MBEDTLS_X509_RSASSA_PSS_SUPPORT(not relevant in psa-crypto)
This issue is about to add the same relevant tests in psa-crypto.
Do we change depends.py to support the psa-crypto configuration and generate the equivalent configurations based on PSAWANT macros? For psa-crypto all.sh purposes we need only cipher_id, cipher_chaining, curves, hashes and pkalgs options. What about the others in the psa-crypto context?
test_dependspy*_psa test components in mbedtls:
This issue is about to add the same relevant tests in psa-crypto. Do we change depends.py to support the psa-crypto configuration and generate the equivalent configurations based on PSAWANT macros? For psa-crypto all.sh purposes we need only cipher_id, cipher_chaining, curves, hashes and pkalgs options. What about the others in the psa-crypto context?
STILL OPEN QUESTIONS IN THIS ISSUE