From cf8e9233f0139f8ebacbfd4fa34ccf410ec8430c Mon Sep 17 00:00:00 2001 From: Benjamin Kaduk Date: Fri, 26 Jan 2018 09:23:57 -0600 Subject: [PATCH] Catch some more old sigalg names in comments Make the sigalg name in comments reflect one that actually exists in the draft standard. Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/5174) --- doc/man3/SSL_CTX_set1_sigalgs.pod | 2 +- test/recipes/70-test_sslsigalgs.t | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/man3/SSL_CTX_set1_sigalgs.pod b/doc/man3/SSL_CTX_set1_sigalgs.pod index a634eb8821..74d06989e1 100644 --- a/doc/man3/SSL_CTX_set1_sigalgs.pod +++ b/doc/man3/SSL_CTX_set1_sigalgs.pod @@ -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 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. The use of MD5 as a digest is strongly discouraged due to security weaknesses. diff --git a/test/recipes/70-test_sslsigalgs.t b/test/recipes/70-test_sslsigalgs.t index d1ed6ec7f4..35531c634b 100644 --- a/test/recipes/70-test_sslsigalgs.t +++ b/test/recipes/70-test_sslsigalgs.t @@ -169,7 +169,7 @@ SKIP: { 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 - # 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 # when we have an API capable of configuring the TLSv1.3 sig algs $proxy->clear(); -- 2.25.1