diff options
author | Xin LI <delphij@FreeBSD.org> | 2013-04-02 17:34:42 +0000 |
---|---|---|
committer | Xin LI <delphij@FreeBSD.org> | 2013-04-02 17:34:42 +0000 |
commit | 0d9d75b124880ee5a3aeb5c2af92a04340c02bef (patch) | |
tree | 953639ad57c000dc6351819b4798541490d39802 /crypto/openssl/doc/ssl/SSL_clear.pod | |
parent | 660eb4006e69a82831062be4a4af070afccf64bc (diff) |
Notes
Diffstat (limited to 'crypto/openssl/doc/ssl/SSL_clear.pod')
-rw-r--r-- | crypto/openssl/doc/ssl/SSL_clear.pod | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/crypto/openssl/doc/ssl/SSL_clear.pod b/crypto/openssl/doc/ssl/SSL_clear.pod index 8e077e31c9a8..d4df1bfac316 100644 --- a/crypto/openssl/doc/ssl/SSL_clear.pod +++ b/crypto/openssl/doc/ssl/SSL_clear.pod @@ -39,10 +39,16 @@ for a description of the method's properties. SSL_clear() resets the SSL object to allow for another connection. The reset operation however keeps several settings of the last sessions (some of these settings were made automatically during the last -handshake). It only makes sense when opening a new session (or reusing -an old one) with the same peer that shares these settings. -SSL_clear() is not a short form for the sequence -L<SSL_free(3)|SSL_free(3)>; L<SSL_new(3)|SSL_new(3)>; . +handshake). It only makes sense for a new connection with the exact +same peer that shares these settings, and may fail if that peer +changes its settings between connections. Use the sequence +L<SSL_get_session(3)|SSL_get_session(3)>; +L<SSL_new(3)|SSL_new(3)>; +L<SSL_set_session(3)|SSL_set_session(3)>; +L<SSL_free(3)|SSL_free(3)> +instead to avoid such failures +(or simply L<SSL_free(3)|SSL_free(3)>; L<SSL_new(3)|SSL_new(3)> +if session reuse is not desired). =head1 RETURN VALUES |