| SSL_clear.pod (76866) | SSL_clear.pod (100928) |
|---|---|
| 1=pod 2 3=head1 NAME 4 5SSL_clear - reset SSL object to allow another connection 6 7=head1 SYNOPSIS 8 --- 11 unchanged lines hidden (view full) --- 20SSL_clear is used to prepare an SSL object for a new connection. While all 21settings are kept, a side effect is the handling of the current SSL session. 22If a session is still B<open>, it is considered bad and will be removed 23from the session cache, as required by RFC2246. A session is considered open, 24if L<SSL_shutdown(3)|SSL_shutdown(3)> was not called for the connection 25or at least L<SSL_set_shutdown(3)|SSL_set_shutdown(3)> was used to 26set the SSL_SENT_SHUTDOWN state. 27 | 1=pod 2 3=head1 NAME 4 5SSL_clear - reset SSL object to allow another connection 6 7=head1 SYNOPSIS 8 --- 11 unchanged lines hidden (view full) --- 20SSL_clear is used to prepare an SSL object for a new connection. While all 21settings are kept, a side effect is the handling of the current SSL session. 22If a session is still B<open>, it is considered bad and will be removed 23from the session cache, as required by RFC2246. A session is considered open, 24if L<SSL_shutdown(3)|SSL_shutdown(3)> was not called for the connection 25or at least L<SSL_set_shutdown(3)|SSL_set_shutdown(3)> was used to 26set the SSL_SENT_SHUTDOWN state. 27 |
| 28If a session was closed cleanly, the session object will be kept and all 29settings corresponding. This explicitly means, that e.g. the special method 30used during the session will be kept for the next handshake. So if the 31session was a TLSv1 session, a SSL client object will use a TLSv1 client 32method for the next handshake and a SSL server object will use a TLSv1 33server method, even if SSLv23_*_methods were chosen on startup. This 34will might lead to connection failures (see L<SSL_new(3)|SSL_new(3)>) 35for a description of the method's properties. 36 37=head1 WARNINGS 38 39SSL_clear() resets the SSL object to allow for another connection. The 40reset operation however keeps several settings of the last sessions 41(some of these settings were made automatically during the last 42handshake). It only makes sense when opening a new session (or reusing 43an old one) with the same peer that shares these settings. 44SSL_clear() is not a short form for the sequence 45L<SSL_free(3)|SSL_free(3)>; L<SSL_new(3)|SSL_new(3)>; . 46 |
|
| 28=head1 RETURN VALUES 29 30The following return values can occur: 31 32=over 4 33 34=item 0 35 36The SSL_clear() operation could not be performed. Check the error stack to 37find out the reason. 38 39=item 1 40 41The SSL_clear() operation was successful. 42 43=back 44 45L<SSL_new(3)|SSL_new(3)>, L<SSL_free(3)|SSL_free(3)>, 46L<SSL_shutdown(3)|SSL_shutdown(3)>, L<SSL_set_shutdown(3)|SSL_set_shutdown(3)>, | 47=head1 RETURN VALUES 48 49The following return values can occur: 50 51=over 4 52 53=item 0 54 55The SSL_clear() operation could not be performed. Check the error stack to 56find out the reason. 57 58=item 1 59 60The SSL_clear() operation was successful. 61 62=back 63 64L<SSL_new(3)|SSL_new(3)>, L<SSL_free(3)|SSL_free(3)>, 65L<SSL_shutdown(3)|SSL_shutdown(3)>, L<SSL_set_shutdown(3)|SSL_set_shutdown(3)>, |
| 47L | 66L<SSL_CTX_set_options(3)|SSL_CTX_set_options(3)>, L<ssl(3)|ssl(3)>, 67L<SSL_CTX_set_client_cert_cb(3)|SSL_CTX_set_client_cert_cb(3)> |
| 48 49=cut | 68 69=cut |