From c636c1c470fd2b4b0cb546e6ee85971375e42ec1 Mon Sep 17 00:00:00 2001 From: Viktor Dukhovni Date: Sat, 2 Apr 2016 16:47:48 -0400 Subject: Fix client verify mode to check SSL_VERIFY_PEER MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The original check for != SSL_VERIFY_NONE can give surprising results when flags SSL_VERIFY_PEER is not set, but other flags are. Note that SSL_VERIFY_NONE (0) is not a flag bit, it is rather the absense of all other flag bits. Signed-off-by: Rob Percival Reviewed-by: Emilia Käsper --- doc/ssl/SSL_CTX_set_verify.pod | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) (limited to 'doc') diff --git a/doc/ssl/SSL_CTX_set_verify.pod b/doc/ssl/SSL_CTX_set_verify.pod index 5da4166949..d60bb6a3ed 100644 --- a/doc/ssl/SSL_CTX_set_verify.pod +++ b/doc/ssl/SSL_CTX_set_verify.pod @@ -89,8 +89,7 @@ B ignored =back -Exactly one of the B flags SSL_VERIFY_NONE and SSL_VERIFY_PEER must be -set at any time. +If the B is SSL_VERIFY_NONE none of the other flags may be set. The actual verification procedure is performed either using the built-in verification procedure or using another application provided verification @@ -146,18 +145,6 @@ Its return value is identical to B, so that any verification failure will lead to a termination of the TLS/SSL handshake with an alert message, if SSL_VERIFY_PEER is set. -=head1 BUGS - -In client mode, it is not checked whether the SSL_VERIFY_PEER flag -is set, but whether SSL_VERIFY_NONE is not set. This can lead to -unexpected behaviour, if the SSL_VERIFY_PEER and SSL_VERIFY_NONE are not -used as required (exactly one must be set at any time). - -The certificate verification depth set with SSL[_CTX]_verify_depth() -stops the verification at a certain depth. The error message produced -will be that of an incomplete certificate chain and not -X509_V_ERR_CERT_CHAIN_TOO_LONG as may be expected. - =head1 RETURN VALUES The SSL*_set_verify*() functions do not provide diagnostic information. -- cgit v1.2.3