Gilles Peskine e7e704ac83 p256-m: allow deterministic ECDSA verification ... For ECDSA verification, there is no difference between the deterministic and randomized algorithm. The PSA core consider the two variants as identical as far as key policies are concerned, and the built-in implementation accepts either variant even if only the other variant is supported for signature. In p256-m, accept to perform an ECDSA verification when the algorithm is specified as deterministic ECDSA. This makes the behavior identical to the built-in implementation, which is less surprising for users and saves us from having to cope with a difference in our testing. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>		2024-12-09 18:31:59 +01:00
..
data_files	p256-m: allow deterministic ECDSA verification	2024-12-09 18:31:59 +01:00
config.py	Remove not TF-PSA-Cripto related symbol	2024-12-05 18:59:11 +01:00
framework_scripts_path.py	Add python module serach path library for TF PSA Crypto	2024-12-05 10:00:40 +01:00
generate_driver_wrappers.py	Move driver wrappers generation to tf-psa-crypto	2024-12-04 14:25:02 +01:00
generate_psa_constants.py	Move generate_psa_constants.py to tf-psa-crypto	2024-11-20 16:20:52 +00:00
project_name.txt	Use scripts/project_name.txt in Python scripts	2024-09-10 10:43:02 +02:00