Searched refs:shutdown (Results 1 – 25 of 61) sorted by relevance
123
6 SSL_get_quiet_shutdown - manipulate shutdown behaviour20 SSL_CTX_set_quiet_shutdown() sets the "quiet shutdown" flag for B<ctx> to be24 SSL_CTX_get_quiet_shutdown() returns the "quiet shutdown" setting of B<ctx>.26 SSL_set_quiet_shutdown() sets the "quiet shutdown" flag for B<ssl> to be32 SSL_get_quiet_shutdown() returns the "quiet shutdown" setting of B<ssl>.41 for a clean shutdown.43 When setting the "quiet shutdown" flag to 1, L<SSL_shutdown(3)>48 The session is thus considered to be shutdown, but no close_notify alert51 The default is normal shutdown behaviour as described by the TLS standard.
40 shutdown process and return 0 to indicate that the shutdown process has not yet59 A close_notify shutdown alert message is sent to the peer.63 A close_notify shutdown alert message is received from the peer.75 responds in turn with a close_notify shutdown alert message.82 application's shutdown indication.158 peer of connection shutdown.318 =item RFC compliant shutdown mode330 =item Rapid shutdown mode382 The shutdown process is ongoing and has not yet completed.396 The shutdown was successfully completed.[all …]
5 SSL_set_shutdown, SSL_get_shutdown - manipulate shutdown state of an SSL connection17 SSL_set_shutdown() sets the shutdown state of B<ssl> to B<mode>.19 SSL_get_shutdown() returns the shutdown mode of B<ssl>.23 The shutdown state of an ssl connection is a bit-mask of:29 No shutdown setting, yet.33 A close_notify shutdown alert was sent to the peer, the connection is being38 A shutdown alert was received form the peer, either a normal close_notify45 The shutdown state of the connection is used to determine the state of66 SSL_get_shutdown() returns the current shutdown state as set or based
36 this BIO's shutdown (i.e. BIO_CLOSE) flag. If set then the underlying resource46 BIO_get_shutdown() returns the stat of the BIO's shutdown (i.e. BIO_CLOSE) flag.
59 at the protocol level or a connection failure occurred. The shutdown was
58 at the protocol level or a connection failure occurred. The shutdown was
86 int (*shutdown) (X509_LOOKUP *ctx)) in X509_LOOKUP_meth_set_shutdown()88 method->shutdown = shutdown; in X509_LOOKUP_meth_set_shutdown()95 return method->shutdown; in X509_LOOKUP_meth_get_shutdown()
79 int (*shutdown) (X509_LOOKUP *ctx); member
103 if (a->shutdown) { in fd_free()163 b->shutdown = (int)num; in fd_ctrl()176 ret = b->shutdown; in fd_ctrl()179 b->shutdown = (int)num; in fd_ctrl()
104 if (a->shutdown) { in sock_free()188 if (b->shutdown) { in sock_ctrl()194 b->shutdown = (int)num; in sock_ctrl()209 ret = b->shutdown; in sock_ctrl()212 b->shutdown = (int)num; in sock_ctrl()
122 if (a->shutdown) { in file_free()209 b->shutdown = (int)num & BIO_CLOSE; in file_ctrl()269 b->shutdown = (int)num & BIO_CLOSE; in file_ctrl()317 ret = (long)b->shutdown; in file_ctrl()320 b->shutdown = (int)num; in file_ctrl()
125 bi->shutdown = 1; in mem_init()162 if (a->shutdown && a->init && a->ptr != NULL) { in mem_buf_free()303 b->shutdown = (int)num; in mem_ctrl()317 ret = (long)b->shutdown; in mem_ctrl()320 b->shutdown = (int)num; in mem_ctrl()
87 bi->shutdown = 1; in acpt_new()123 shutdown(c->accept_sock, 2); in acpt_close_socket()138 if (a->shutdown) { in acpt_free()474 b->shutdown = (int)num; in acpt_ctrl()523 ret = b->shutdown; in acpt_ctrl()526 b->shutdown = (int)num; in acpt_ctrl()
90 bio->shutdown = 1; in BIO_new_ex()174 a->shutdown = shut; in BIO_set_shutdown()179 return a->shutdown; in BIO_get_shutdown()878 new_bio->shutdown = bio->shutdown; in BIO_dup_chain()
108 int shutdown; member
340 shutdown(bio->num, 2); in conn_close_socket()356 if (a->shutdown) { in conn_free()658 ret = b->shutdown; in conn_ctrl()661 b->shutdown = (int)num; in conn_ctrl()
306 if (sc->shutdown & SSL_RECEIVED_SHUTDOWN) { in dtls1_read_bytes()368 sc->shutdown |= SSL_RECEIVED_SHUTDOWN; in dtls1_read_bytes()436 sc->shutdown |= SSL_RECEIVED_SHUTDOWN; in dtls1_read_bytes()445 sc->shutdown |= SSL_RECEIVED_SHUTDOWN; in dtls1_read_bytes()458 if (sc->shutdown & SSL_SENT_SHUTDOWN) { /* but we have not received a in dtls1_read_bytes()
736 if (s->shutdown & SSL_RECEIVED_SHUTDOWN) { in ssl3_read_bytes()905 s->shutdown |= SSL_RECEIVED_SHUTDOWN; in ssl3_read_bytes()913 s->shutdown |= SSL_RECEIVED_SHUTDOWN; in ssl3_read_bytes()938 if ((s->shutdown & SSL_SENT_SHUTDOWN) != 0) { in ssl3_read_bytes()
4 $ ! P1 startup / setup / shutdown scripts directory
9 $ ! P5 startup / setup / shutdown scripts directory
1 $ ! OpenSSL shutdown script
128 shutdown
58 if (s->shutdown & SSL_SENT_SHUTDOWN && desc != SSL_AD_CLOSE_NOTIFY) in ssl3_send_alert()
325 As in the TLS blocking example we must shutdown the connection when we are328 If our application was initiating the shutdown then we would expect to see331 the shutdown). In this particular example we don't expect SSL_shutdown() to333 has shutdown already. So we just keep calling it until SSL_shutdown() returns 1.340 * The peer already shutdown gracefully (we know this because of the
672 goto shutdown; in test_hashtable_multithread()675 shutdown: in test_hashtable_multithread()
Completed in 33 milliseconds