Searched refs:stateless (Results 1 – 16 of 16) sorted by relevance
24 - optionally trigger sending stateless reset packets if a received packet47 - optionally trigger sending stateless reset packets as above for client
134 the appropriate Connection ID and optionally schedules sending stateless
179 - the Terminated state if the peer triggers a stateless reset; a219 idle timeout, stateless reset), a connection always ultimately ends up in this465 - `RX:STATELESS_RESET` indicates receipt of a stateless reset, but note466 that it is not guaranteed that we are able to recognise a stateless reset
51 - The BIO methods are designed to support stateless operation in which they81 stateless and not requiire locking. Therefore the OS-native iovec structures431 “stateless” (it's just a simple call to `recvfrom`, and doesn't require mutation
112 unsigned char reset_token[16]; /* stateless reset token is per conn ID */
408 the FIFD (`QUIC_FIFD`). The FIFD is completely stateless and provides reasonable
11 These API items do not relate to SSL objects. They may be stateless or may
1239 as such operates in a stateless fashion with regards to a BIO. This means, for
310 SSL/TLS supports two mechanisms for resuming sessions: session ids and stateless318 When using stateless session tickets the server uses a session ticket encryption327 and stateless. Stateless tickets work the same way as in TLSv1.2 and below.331 presents a ticket in the same way as for stateless tickets. The server can then335 By default OpenSSL will use stateless tickets. The SSL_OP_NO_TICKET option will336 cause stateless tickets to not be issued. In TLSv1.2 and below this means no340 In TLSv1.3 it is possible to suppress all tickets (stateful and stateless) from
45 This timeout value is used as the ticket lifetime hint for stateless session
9 - Callback functions for stateless TLS1.3 cookies
42 As a countermeasure to this issue TLSv1.3 and DTLS include a stateless cookie
84 L<BIO_recvmmsg(3)> methods are stateless and do not cause the internal state of
119 static int stateless = 0; variable1588 stateless = 1; in s_server_main()1748 if (stateless && socket_type != SOCK_STREAM) { in s_server_main()2951 if (dtlslisten || stateless) { in init_ssl_connection()2983 stateless = 0; in init_ssl_connection()3026 if (((dtlslisten || stateless) && i == 0) in init_ssl_connection()3027 || (!dtlslisten && !stateless && retry)) { in init_ssl_connection()
141 [B<-stateless>]840 =item B<-stateless>
7363 The DTLSv1_listen function is intended to be stateless and processes the11254 * Fixes to stateless session resumption handling. Use initial_ctx when11257 stateless session resumption: this makes it possible to determine if
Completed in 82 milliseconds
