Searched refs:SSL_clear (Results 1 – 25 of 26) sorted by relevance
12
/openssl/doc/man3/ |
H A D | SSL_clear.pod | 5 SSL_clear - reset SSL object to allow another connection 11 int SSL_clear(SSL *ssl); 20 SSL_clear is used to prepare an SSL object for a new connection. While all 42 SSL_clear() resets the SSL object to allow for another connection. The 64 The SSL_clear() operation could not be performed. Check the error stack to 69 The SSL_clear() operation was successful.
|
H A D | SSL_CTX_set_ssl_version.pod | 24 SSL_CTX with L<SSL_new(3)> are not affected, except when L<SSL_clear(3)> is 31 object. It may be reset, when SSL_clear() is called. 41 When L<SSL_clear(3)> is called and no session is connected to 77 L<SSL_clear(3)>, L<ssl(7)>,
|
H A D | SSL_CTX_set_quiet_shutdown.pod | 29 It is not changed when L<SSL_clear(3)> is called. 65 L<SSL_clear(3)>, L<SSL_free(3)>
|
H A D | SSL_CTX_set_client_cert_cb.pod | 61 object. It will not be reset by calling L<SSL_clear(3)>. 90 even when L<SSL_clear(3)> is being called. It is therefore 99 L<SSL_clear(3)>, L<SSL_free(3)>
|
H A D | SSL_set_shutdown.pod | 47 L<SSL_clear(3)> or L<SSL_free(3)> is called, 80 L<SSL_clear(3)>, L<SSL_free(3)>
|
H A D | SSL_new.pod | 37 use L<SSL_clear(3)> to recycle an SSL handle that is not in its initial 123 L<SSL_free(3)>, L<SSL_clear(3)>,
|
H A D | SSL_get_session.pod | 64 the connection is in use. If L<SSL_clear(3)> or 101 L<SSL_clear(3)>,
|
H A D | SSL_alloc_buffers.pod | 58 L<SSL_free(3)>, L<SSL_clear(3)>,
|
H A D | SSL_CTX_set_cert_cb.pod | 69 L<SSL_clear(3)>, L<SSL_free(3)>
|
H A D | SSL_free.pod | 73 L<SSL_new(3)>, L<SSL_clear(3)>,
|
H A D | SSL_CTX_use_certificate.pod | 64 L<SSL_clear(3)> is called for this SSL object. 189 L<ssl(7)>, L<SSL_new(3)>, L<SSL_clear(3)>,
|
H A D | SSL_shutdown.pod | 156 simply calling L<SSL_free(3)> or L<SSL_clear(3)> as calling SSL_shutdown() 423 L<SSL_clear(3)>, L<SSL_free(3)>,
|
H A D | SSL_CTX_set_options.pod | 60 SSL objects. SSL_clear() does not affect the settings. 521 L<ssl(7)>, L<SSL_new(3)>, L<SSL_clear(3)>, L<SSL_shutdown(3)>
|
/openssl/ssl/ |
H A D | bio_ssl.c | 252 if (!SSL_clear(ssl)) { in ssl_ctrl()
|
H A D | d1_lib.c | 441 if (!SSL_clear(ssl)) in DTLSv1_listen()
|
H A D | ssl_lib.c | 569 int SSL_clear(SSL *s) in SSL_clear() function 7228 if (!SSL_clear(s)) in SSL_stateless()
|
/openssl/ssl/statem/ |
H A D | statem.c | 380 if ((s->s3.flags & TLS1_FLAGS_STATELESS) == 0 && !SSL_clear(ssl)) in state_machine()
|
/openssl/doc/designs/quic-design/ |
H A D | quic-api.md | 25 - [`SSL_clear`](#-ssl-clear-) 287 #### `SSL_clear` 295 >SSL_clear() resets the SSL object to allow for another connection. The reset 301 **TBD:** How should `SSL_clear` be implemented? Either: 305 - Preserve `SSL_clear` semantics at the handshake layer, reset all QUIC state
|
H A D | quic-api-ssl-funcs.md | 615 | `SSL_clear` (connection) | CSSM | U | FC | QSI | Done … 616 | `SSL_clear` (stream) | CSSM | U | FC | QSI | Done … 988 ### What should `SSL_dup` and `SSL_clear` do?
|
/openssl/util/ |
H A D | libssl.num | 126 SSL_clear 127 3_0_0 EXIST::FUNCTION:
|
/openssl/doc/ |
H A D | build.info | 2530 DEPEND[html/man3/SSL_clear.html]=man3/SSL_clear.pod 2531 GENERATE[html/man3/SSL_clear.html]=man3/SSL_clear.pod 2532 DEPEND[man/man3/SSL_clear.3]=man3/SSL_clear.pod 2533 GENERATE[man/man3/SSL_clear.3]=man3/SSL_clear.pod 3642 html/man3/SSL_clear.html \ 4306 man/man3/SSL_clear.3 \
|
/openssl/test/ |
H A D | quicapitest.c | 760 if (!TEST_false(SSL_clear(ssl))) in test_quic_forbidden_options()
|
H A D | sslapitest.c | 1005 if (!TEST_true(SSL_clear(serverssl))) in execute_test_large_message() 7212 if (!TEST_true(SSL_clear(serverssl))) in test_ssl_clear() 7233 if (!TEST_true(SSL_clear(clientssl))) in test_ssl_clear()
|
/openssl/apps/ |
H A D | s_server.c | 2483 if (!SSL_clear(con)) { in sv_body()
|
/openssl/include/openssl/ |
H A D | ssl.h.in | 1570 __owur int SSL_clear(SSL *s);
|
Completed in 122 milliseconds
12