mirror of
https://github.com/openssl/openssl.git
synced 2025-01-06 13:26:43 +08:00
22f0c72b92
The actual functionality of generating signatures through the `EVP_PKEY`
API is completely untested.
Current tests under the `EVP_PKEY` API
(`test/recipes/30-test_evp_data/evppkey.txt`) only cover `Verify` and
`Decrypt`, while encryption and signature generation are tested with
ad-hoc clients (`test/sm2crypttest.c`, `test/sm2signtest.c`) that do not
call the `EVP_PKEY` interface at all but soon-to-be private functions
that bypass it (cf. PR#5895 ).
It is my opinion that an ideal solution for the future would consist on
enhancing the `test/evp_pkey` facility and syntax to allow tests to take
control of the PRNG to inject known nonces and validate the results of
`EVP_PKEY` implementations against deterministic known answer tests, but
it is probably too late to work on this feature in time for next release.
Given that commit
|
||
---|---|---|
.. | ||
evpciph.txt | ||
evpdigest.txt | ||
evpencod.txt | ||
evpkdf.txt | ||
evpmac.txt | ||
evppbe.txt | ||
evppkey.txt |