QuasarApp/openssl
4
0
Fork 0
mirror of https://github.com/QuasarApp/openssl.git synced 2025-04-29 19:24:37 +00:00
Code Issues Projects Releases Wiki Activity

Catch some more old sigalg names in comments

Browse Source 
Make the sigalg name in comments reflect one that actually exists
in the draft standard.

Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5174)
This commit is contained in:
Benjamin Kaduk 2018-01-26 09:23:57 -06:00
parent 36c91d13d1
commit cf8e9233f0
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/man3/SSL_CTX_set1_sigalgs.pod
View File

@ -78,7 +78,7 @@ The short or long name values for digests can be used in a string (for
example "MD5", "SHA1", "SHA224", "SHA256", "SHA384", "SHA512") and example "MD5", "SHA1", "SHA224", "SHA256", "SHA384", "SHA512") and
the public key algorithm strings "RSA", "RSA-PSS", "DSA" or "ECDSA". the public key algorithm strings "RSA", "RSA-PSS", "DSA" or "ECDSA".
The TLS 1.3 signature scheme names (such as "rsa_pss_sha256") can also The TLS 1.3 signature scheme names (such as "rsa_pss_pss_sha256") can also
be used with the B<_list> forms of the API. be used with the B<_list> forms of the API.
The use of MD5 as a digest is strongly discouraged due to security weaknesses. The use of MD5 as a digest is strongly discouraged due to security weaknesses.

2
test/recipes/70-test_sslsigalgs.t
View File

@ -169,7 +169,7 @@ SKIP: {
ok(TLSProxy::Message->success, "PSS only sigalgs in TLSv1.2"); ok(TLSProxy::Message->success, "PSS only sigalgs in TLSv1.2");
#Test 14: Responding with a sig alg we did not send in TLSv1.2 should fail #Test 14: Responding with a sig alg we did not send in TLSv1.2 should fail
# We send rsa_pkcs1_sha256 and respond with rsa_pss_sha256 # We send rsa_pkcs1_sha256 and respond with rsa_pss_rsae_sha256
# TODO(TLS1.3): Add a similar test to the TLSv1.3 section above # TODO(TLS1.3): Add a similar test to the TLSv1.3 section above
# when we have an API capable of configuring the TLSv1.3 sig algs # when we have an API capable of configuring the TLSv1.3 sig algs
$proxy->clear(); $proxy->clear();