Lines Matching +full:3 +full:a

72 The QUIC protocol maps to the standard SSL API. A QUIC connection is represented
73 by an SSL object in the same way that a TLS connection is. Only minimal changes
75 support in. QUIC clients can use \fBOSSL_QUIC_client_method\fR\|(3) or
76 \&\fBOSSL_QUIC_client_thread_method\fR\|(3) with \fBSSL_CTX_new\fR\|(3). See below for more
78 option: SSL method \fBOSSL_QUIC_server_method\fR\|(3) with \fBSSL_CTX_new\fR\|(3).
95 When a client creates a QUIC connection, by default, it operates in default
97 application usage patterns. In this mode, the connection has a single stream
98 associated with it. Calls to \fBSSL_read\fR\|(3) and \fBSSL_write\fR\|(3) on the QUIC
100 client-initiated or server-initiated from a QUIC perspective depends on whether
101 \&\fBSSL_read\fR\|(3) or \fBSSL_write\fR\|(3) is called first.
109 A QUIC client connection can be used in either default stream mode or
110 multi-stream mode. By default, a newly created QUIC connection SSL object uses
113 In default stream mode, a stream is implicitly created and bound to the QUIC
114 connection SSL object; \fBSSL_read\fR\|(3) and \fBSSL_write\fR\|(3) calls to the QUIC
117 When default stream mode is used, any API function which can be called on a QUIC
118 stream SSL object can also be called on a QUIC connection SSL object, in which
121 The identity of a QUIC stream, including its stream ID, varies depending on
122 whether a stream is client-initiated or server-initiated. In default stream
123 mode, if a client application calls \fBSSL_read\fR\|(3) first before any call to
124 \&\fBSSL_write\fR\|(3) on the connection, it is assumed that the application protocol
125 is using a server-initiated stream, and the \fBSSL_read\fR\|(3) call will not
127 configured) until the server initiates a stream. Conversely, if the client
128 application calls \fBSSL_write\fR\|(3) before any call to \fBSSL_read\fR\|(3) on the
129 connection, it is assumed that a client-initiated stream is to be used
130 and such a stream is created automatically.
137 \&\fBSSL_new_stream\fR\|(3) and \fBSSL_accept_stream\fR\|(3); note that the default incoming
138 stream policy will need to be changed using \fBSSL_set_incoming_stream_policy\fR\|(3)
139 in order to use \fBSSL_accept_stream\fR\|(3) in this case. However, applications
143 Calling \fBSSL_new_stream\fR\|(3) or \fBSSL_accept_stream\fR\|(3) before a default stream
145 creation of a default stream.
150 and attempts to call \fBSSL_read\fR\|(3) and \fBSSL_write\fR\|(3) on the QUIC connection
151 SSL object fail. Instead, an application calls \fBSSL_new_stream\fR\|(3) or
152 \&\fBSSL_accept_stream\fR\|(3) to create individual stream SSL objects for sending and
153 receiving application data using \fBSSL_read\fR\|(3) and \fBSSL_write\fR\|(3).
155 To use multi-stream mode, call \fBSSL_set_default_stream_mode\fR\|(3) with an
158 initiating a connection.
161 with the connection, calls to API functions which are defined as operating on a
163 such as \fBSSL_write\fR\|(3) or \fBSSL_get_stream_id\fR\|(3) will fail.
166 Most SSL APIs, such as \fBSSL_read\fR\|(3) and \fBSSL_write\fR\|(3), function as they do
170 Since QUIC uses UDP, \fBSSL_set_bio\fR\|(3), \fBSSL_set0_rbio\fR\|(3) and
171 \&\fBSSL_set0_wbio\fR\|(3) function as before, but must now receive a BIO with datagram
172 semantics. There are broadly four options for applications to use as a network
176 \&\fBBIO_s_datagram\fR\|(3), recommended for most applications, replaces
177 \&\fBBIO_s_socket\fR\|(3) and provides a UDP socket.
179 \&\fBBIO_s_dgram_pair\fR\|(3) provides BIO pair-like functionality but with datagram
180 semantics, and is recommended for existing applications which use a BIO pair or
183 \&\fBBIO_s_dgram_mem\fR\|(3) provides a simple memory BIO-like interface but with
184 datagram semantics. Unlike \fBBIO_s_dgram_pair\fR\|(3), it is unidirectional.
186 An application may also choose to implement a custom BIO. The new
187 \&\fBBIO_sendmmsg\fR\|(3) and \fBBIO_recvmmsg\fR\|(3) APIs must be supported.
192 \&\fBSSL_set_fd\fR\|(3), \fBSSL_set_rfd\fR\|(3) and \fBSSL_set_wfd\fR\|(3) traditionally
193 instantiate a \fBBIO_s_socket\fR\|(3). For QUIC, these functions instead instantiate
194 a \fBBIO_s_datagram\fR\|(3). This is equivalent to instantiating a
195 \&\fBBIO_s_datagram\fR\|(3) and using \fBSSL_set0_rbio\fR\|(3) and \fBSSL_set0_wbio\fR\|(3).
197 Traditionally, whether the application-level I/O APIs (such as \fBSSL_read\fR\|(3)
198 and \fBSSL_write\fR\|(3) operated in a blocking fashion was directly correlated with
199 whether the underlying network socket was configured in a blocking fashion. This
201 application-level blocking mode using \fBSSL_set_blocking_mode\fR\|(3). See
202 \&\fBSSL_set_blocking_mode\fR\|(3) for details.
204 Network-level I/O must always be performed in a nonblocking manner. The
206 I/O functions such as \fBSSL_read\fR\|(3) and \fBSSL_write\fR\|(3), but the underlying
207 network BIO provided to QUIC (such as a \fBBIO_s_datagram\fR\|(3)) must be configured
209 \&\fBSSL_set_blocking_mode\fR\|(3).
211 \&\fBBIO_new_ssl_connect\fR\|(3) has been changed to automatically use a
212 \&\fBBIO_s_datagram\fR\|(3) when used with QUIC, therefore applications which use this
215 \&\fBBIO_new_buffer_ssl_connect\fR\|(3) cannot be used with QUIC and applications must
216 change to use \fBBIO_new_ssl_connect\fR\|(3) instead.
218 \&\fBSSL_shutdown\fR\|(3) has significant changes in relation to how QUIC connections
222 after their usage of a QUIC connection is completed. A rapid shutdown mode
223 is available for such applications. For details, see \fBSSL_shutdown\fR\|(3).
225 \&\fBSSL_want\fR\|(3), \fBSSL_want_read\fR\|(3) and \fBSSL_want_write\fR\|(3) no longer reflect
231 receive part of a QUIC stream does not currently have any more data available to
236 incoming network datagrams, use the new function \fBSSL_net_read_desired\fR\|(3);
239 \&\fBSSL_net_write_desired\fR\|(3). Only applications which wish to manage their own event
245 \&\fBSSL_set_alpn_protos\fR\|(3).
247 Whether QUIC operates in a client or server mode is determined by the
248 \&\fBSSL_METHOD\fR used, rather than by calls to \fBSSL_set_connect_state\fR\|(3) or
249 \&\fBSSL_set_accept_state\fR\|(3). It is not necessary to call either of
250 \&\fBSSL_set_connect_state\fR\|(3) or \fBSSL_set_accept_state\fR\|(3) before connecting, but
254 The \fBSSL_set_min_proto_version\fR\|(3) and \fBSSL_set_max_proto_version\fR\|(3) APIs are
265 Record Padding and Fragmentation (\fBSSL_set_block_padding\fR\|(3), etc.)
267 \&\fBSSL_stateless\fR\|(3) support
271 TLSv1.3 Early Data
278 QUIC requires the use of TLSv1.3 or later, therefore functionality only relevant
281 Some cipher suites which are generally available for TLSv1.3 are not available
292 Readahead (\fBSSL_set_read_ahead\fR\|(3), etc.)
301 A client application wishing to use QUIC must use \fBOSSL_QUIC_client_method\fR\|(3)
302 or \fBOSSL_QUIC_client_thread_method\fR\|(3) as its SSL method. For more information
306 A server application wishing to use QUIC must use \fBOSSL_QUIC_server_method\fR\|(3). 
307 The server can then accept new connections with \fBSSL_accept_connection\fR\|(3).
313 Your application uses \fBBIO_s_socket\fR\|(3) to construct a BIO which is passed to
316 Changes needed: Change your application to use \fBBIO_s_datagram\fR\|(3) instead when
318 not need to use \fBSSL_set1_initial_peer_addr\fR\|(3) to set the initial peer
321 Your application uses \fBBIO_new_ssl_connect\fR\|(3) to
322 construct a BIO which is passed to the SSL object to provide it with network
325 Changes needed: No changes needed. Use of QUIC is detected automatically and a
326 datagram socket is created instead of a normal TCP socket.
328 Your application uses any other I/O strategy in this list but combines it with a
329 \&\fBBIO_f_buffer\fR\|(3), for example using \fBBIO_push\fR\|(3).
331 Changes needed: Disable the usage of \fBBIO_f_buffer\fR\|(3) when using QUIC. Usage
332 of such a buffer is incompatible with QUIC as QUIC requires datagram semantics
335 Your application uses a BIO pair to cause the SSL object to read and write
336 network traffic to a memory buffer. Your application manages the transmission
337 and reception of buffered data itself in a way unknown to libssl.
339 Changes needed: Switch from using a conventional BIO pair to using
340 \&\fBBIO_s_dgram_pair\fR\|(3) instead, which has the necessary datagram semantics. You
341 will need to modify your application to transmit and receive using a UDP socket
342 and to use datagram semantics when interacting with the \fBBIO_s_dgram_pair\fR\|(3)
345 Your application uses a custom BIO method to provide the SSL object with network
349 semantics. \fBBIO_sendmmsg\fR\|(3) and \fBBIO_recvmmsg\fR\|(3) must be implemented. These
350 calls must operate in a nonblocking fashion. Optionally, implement the
351 \&\fBBIO_get_rpoll_descriptor\fR\|(3) and \fBBIO_get_wpoll_descriptor\fR\|(3) methods if
361 operates in blocking or nonblocking mode. QUIC requires the use of a
364 \&\fBSSL_set_blocking_mode\fR\|(3) API. The default mode is blocking. If an application
365 wishes to use the SSL object APIs at application level in a nonblocking manner,
366 it must add a call to \fBSSL_set_blocking_mode\fR\|(3) to disable blocking mode.
370 \&\fBSSL_read\fR\|(3) or \fBSSL_write\fR\|(3)), or the new function \fBSSL_handle_events\fR\|(3),
373 timer events required by QUIC are handled in a timely fashion.
375 Most applications will service the SSL object by calling \fBSSL_read\fR\|(3) or
376 \&\fBSSL_write\fR\|(3) regularly. If an application does not do this, it should ensure
377 that \fBSSL_handle_events\fR\|(3) is called regularly.
379 \&\fBSSL_get_event_timeout\fR\|(3) can be used to determine when
380 \&\fBSSL_handle_events\fR\|(3) must next be called.
383 (such as \fBBIO_s_datagram\fR\|(3)), the application can use
384 \&\fBSSL_get_rpoll_descriptor\fR\|(3), \fBSSL_get_wpoll_descriptor\fR\|(3) to obtain
385 resources which can be used to determine when \fBSSL_handle_events\fR\|(3) should be
390 are handled in a timely manner. See \fBTHREAD ASSISTED MODE\fR for details.
392 Ensure that your usage of \fBSSL_want\fR\|(3), \fBSSL_want_read\fR\|(3) and
393 \&\fBSSL_want_write\fR\|(3) reflects the API changes described in \fBCHANGES TO EXISTING
394 APIS\fR. In particular, you should use these APIs to determine the ability of a
398 Evaluate your application's use of \fBSSL_shutdown\fR\|(3) in light of the changes
401 \&\fBSSL_shutdown_ex\fR\|(3) API instead. See \fBQUIC-SPECIFIC APIS\fR for details.
408 level (configured using \fBSSL_set_blocking_mode\fR\|(3)).
414 a network socket (e.g. via \fBBIO_s_datagram\fR\|(3)) or whether it intends to buffer
415 transmitted and received datagrams via a \fBBIO_s_dgram_pair\fR\|(3) or custom BIO.
428 QUIC-specific functionality. For example, \fBSSL_stream_conclude\fR\|(3) can be used
429 to indicate the end of the sending part of a stream, and \fBSSL_shutdown_ex\fR\|(3)
430 can be used to provide a QUIC application error code when closing a connection.
434 by calling \fBSSL_set_default_stream_mode\fR\|(3); see the MODES OF OPERATION section
442 .IP \fBSSL_get_event_timeout\fR\|(3) 4
444 Determines when the QUIC implementation should next be woken up via a call to
445 \&\fBSSL_handle_events\fR\|(3) (or another I/O function such as \fBSSL_read\fR\|(3) or
446 \&\fBSSL_write\fR\|(3)), if ever.
448 This can also be used with DTLS and supersedes \fBDTLSv1_get_timeout\fR\|(3) for new
450 .IP \fBSSL_handle_events\fR\|(3) 4
452 This is a non-specific I/O operation which makes a best effort attempt to
456 functions on an SSL object, such as \fBSSL_read\fR\|(3) and \fBSSL_write\fR\|(3),
460 This can also be used with DTLS and supersedes \fBDTLSv1_handle_timeout\fR\|(3) for
464 .IP \fBSSL_new_listener\fR\|(3) 4
466 Creates a listener SSL object, which differs from an ordinary SSL object in that
468 in a protocol-agnostic manner.
473 .IP \fBSSL_new_listener_from\fR\|(3) 4
475 Creates a listener SSL object which is subordinate to a QUIC domain SSL object
476 \&\fIssl\fR. See \fBSSL_new_domain\fR\|(3) and \fBopenssl\-quic\-concurrency\fR\|(7) for details
478 .IP \fBSSL_is_listener\fR\|(3) 4
480 Returns 1 if and only if an SSL object is a listener SSL object.
481 .IP \fBSSL_get0_listener\fR\|(3) 4
485 .IP \fBSSL_listen\fR\|(3) 4
487 Begin listening after a listener has been created. It is ordinarily not needed
489 \&\fBSSL_accept_connection\fR\|(3).
490 .IP \fBSSL_accept_connection\fR\|(3) 4
492 Accepts a new incoming connection for a listner SSL object. A new SSL object
496 .IP \fBSSL_get_accept_connection_queue_len\fR\|(3) 4
500 .IP \fBSSL_new_from_listener\fR\|(3) 4
502 Creates a client connection under a given listener SSL object. For QUIC, it is
503 also possible to use \fBSSL_new_from_listener()\fR in conjunction with a listener
505 \&\fBSSL_LISTENER_FLAG_NO_ACCEPT\fR), leading to a UDP network endpoint which has
507 .IP \fBSSL_new_domain\fR\|(3) 4
509 Creates a new QUIC event domain, represented as an SSL object. This is known as
510 a QUIC domain SSL object. The concept of a QUIC event domain is discussed in
512 .IP \fBSSL_is_domain\fR\|(3) 4
514 Returns 1 if an SSL object is a QUIC domain SSL object.
515 .IP \fBSSL_get0_domain\fR\|(3) 4
517 \&\fBSSL_get0_domain()\fR obtains a pointer to the QUIC domain SSL object in an SSL
519 .IP "\fBSSL_set_blocking_mode\fR\|(3), \fBSSL_get_blocking_mode\fR\|(3)" 4
522 determines whether calls to functions such as \fBSSL_read\fR\|(3) and \fBSSL_write\fR\|(3)
524 .IP "\fBSSL_get_rpoll_descriptor\fR\|(3), \fBSSL_get_wpoll_descriptor\fR\|(3)" 4
529 supports polling, \fBSSL_get_rpoll_descriptor\fR\|(3) outputs an OS resource which
531 a call to \fBSSL_handle_events\fR\|(3). \fBSSL_get_wpoll_descriptor\fR\|(3) works in an
535 \&\fBSSL_net_read_desired\fR\|(3) and \fBSSL_net_write_desired\fR\|(3) return 1,
537 .IP "\fBSSL_net_read_desired\fR\|(3), \fBSSL_net_write_desired\fR\|(3)" 4
540 conjunction with \fBSSL_get_rpoll_descriptor\fR\|(3) and
541 \&\fBSSL_get_wpoll_descriptor\fR\|(3) respectively. They determine whether the
543 .IP \fBSSL_set1_initial_peer_addr\fR\|(3) 4
548 autodetected in some cases. See \fBSSL_set1_initial_peer_addr\fR\|(3) for details.
549 .IP \fBSSL_shutdown_ex\fR\|(3) 4
551 This augments \fBSSL_shutdown\fR\|(3) by allowing an application error code to be
552 specified. It also allows an application to decide how quickly it wants a
554 .IP \fBSSL_stream_conclude\fR\|(3) 4
556 This allows an application to indicate the normal end of the sending part of a
558 part of a stream remains usable.
559 .IP \fBSSL_stream_reset\fR\|(3) 4
562 part of a stream. This corresponds to the RESET_STREAM frame in the QUIC RFC.
563 .IP "\fBSSL_get_stream_write_state\fR\|(3) and \fBSSL_get_stream_read_state\fR\|(3)" 4
566 sending and receiving parts of a stream respectively.
567 .IP "\fBSSL_get_stream_write_error_code\fR\|(3) and \fBSSL_get_stream_read_error_code\fR\|(3)" 4
570 signalled by a peer which has performed a non-normal stream termination of the
571 respective sending or receiving part of a stream, if any.
572 .IP \fBSSL_get_conn_close_info\fR\|(3) 4
576 .IP \fBSSL_get0_connection\fR\|(3) 4
578 Gets the QUIC connection SSL object from a QUIC stream SSL object.
579 .IP \fBSSL_is_connection\fR\|(3) 4
581 Returns 1 if an SSL object is not a QUIC stream SSL object.
582 .IP \fBSSL_get_stream_type\fR\|(3) 4
586 .IP \fBSSL_get_stream_id\fR\|(3) 4
588 Returns the QUIC stream ID which the QUIC protocol has associated with a QUIC
590 .IP \fBSSL_new_stream\fR\|(3) 4
592 Creates a new QUIC stream SSL object representing a new, locally-initiated QUIC
594 .IP \fBSSL_accept_stream\fR\|(3) 4
596 Potentially yields a new QUIC stream SSL object representing a new
599 .IP \fBSSL_get_accept_stream_queue_len\fR\|(3) 4
602 .IP \fBSSL_set_incoming_stream_policy\fR\|(3) 4
606 or allow them to be handled using \fBSSL_accept_stream\fR\|(3).
607 .IP \fBSSL_set_default_stream_mode\fR\|(3) 4
614 .IP \fBBIO_s_dgram_pair\fR\|(3) 4
616 This is a new BIO method which is similar to a conventional BIO pair but
618 .IP "\fBBIO_get_rpoll_descriptor\fR\|(3), \fBBIO_get_wpoll_descriptor\fR\|(3)" 4
620 This is a new BIO API which allows a BIO to expose a poll descriptor. This API
621 is used to implement the corresponding SSL APIs \fBSSL_get_rpoll_descriptor\fR\|(3)
622 and \fBSSL_get_wpoll_descriptor\fR\|(3).
623 .IP "\fBBIO_sendmmsg\fR\|(3), \fBBIO_recvmmsg\fR\|(3)" 4
625 This is a new BIO API which can be implemented by BIOs which implement datagram
626 semantics. It is implemented by \fBBIO_s_datagram\fR\|(3) and \fBBIO_s_dgram_pair\fR\|(3).
628 .IP "\fBBIO_dgram_set_no_trunc\fR\|(3), \fBBIO_dgram_get_no_trunc\fR\|(3)" 4
630 By default, \fBBIO_s_dgram_pair\fR\|(3) has semantics comparable to those of Berkeley
634 .IP "\fBBIO_dgram_set_caps\fR\|(3), \fBBIO_dgram_get_caps\fR\|(3)" 4
636 These functions are used to allow the user of one end of a
637 \&\fBBIO_s_dgram_pair\fR\|(3) to indicate its capabilities to the other end of a
638 \&\fBBIO_s_dgram_pair\fR\|(3). In particular, this allows an application to inform the
642 …O_dgram_get_local_addr_cap\fR\|(3), \fBBIO_dgram_set_local_addr_enable\fR\|(3), \fBBIO_dgram_get_l…
644 Local addressing support refers to the ability of a BIO with datagram semantics
645 to allow a source address to be specified on transmission and to report the
646 destination address on reception. These functions can be used to determine if a
649 .IP \fBBIO_err_is_non_fatal\fR\|(3) 4
651 This is used to determine if an error while calling \fBBIO_sendmmsg\fR\|(3) or
652 \&\fBBIO_recvmmsg\fR\|(3) is ephemeral in nature, such as "would block" errors.
656 \&\fBOSSL_QUIC_client_thread_method\fR\|(3). In this mode, a background thread is
658 for ensuring that timeout events are handled on a timely basis even if no SSL
659 I/O function such as \fBSSL_read\fR\|(3) or \fBSSL_write\fR\|(3) is called by the
660 application for a long time.
671 The implementation may or may not use a common thread or thread pool to service
676 to use the SSL APIs in a blocking fashion, but is also designed to facilitate
677 applications which wish to use the SSL APIs in a nonblocking fashion and manage
683 \&\fBBIO_get_rpoll_descriptor\fR\|(3) for details. Broadly, a \fBBIO_POLL_DESCRIPTOR\fR is
684 a structure which expresses some kind of OS resource which can be used to
685 synchronise on I/O events. The QUIC implementation provides a
694 the SSL object using \fBSSL_set0_rbio\fR\|(3) and \fBSSL_set0_wbio\fR\|(3). This could be
695 a BIO abstracting a network socket such as \fBBIO_s_datagram\fR\|(3), or a BIO
696 abstracting some kind of memory buffer such as \fBBIO_s_dgram_pair\fR\|(3). Use of a
700 \&\fBSSL_set_blocking_mode\fR\|(3).
703 using \fBSSL_set1_initial_peer_addr\fR\|(3), and trigger the connection process by
704 calling \fBSSL_connect\fR\|(3).
707 a \fBBIO_s_datagram\fR\|(3), or a custom BIO which implements
708 \&\fBBIO_get_rpoll_descriptor\fR\|(3) and \fBBIO_get_wpoll_descriptor\fR\|(3)), it should
712 The application should call \fBSSL_get_rpoll_descriptor\fR\|(3) and
713 \&\fBSSL_get_wpoll_descriptor\fR\|(3) to identify OS resources which can be used for
716 It should call \fBSSL_net_read_desired\fR\|(3) and \fBSSL_net_write_desired\fR\|(3) to determine
719 \&\fBSSL_get_event_timeout\fR\|(3) to determine if any timeout event will become
725 The poll descriptor returned by \fBSSL_get_rpoll_descriptor\fR\|(3) becomes readable
726 (if \fBSSL_net_read_desired\fR\|(3) returned 1);
728 The poll descriptor returned by \fBSSL_get_wpoll_descriptor\fR\|(3) becomes writable
729 (if \fBSSL_net_write_desired\fR\|(3) returned 1);
731 The timeout returned by \fBSSL_get_event_timeout\fR\|(3) (if any) expires.
735 Once any of these events occurs, \fBSSL_handle_events\fR\|(3) should be called.
742 the case of \fBBIO_s_dgram_pair\fR\|(3)), the application is responsible for managing
743 and synchronising network I/O. It should call \fBSSL_handle_events\fR\|(3) after it
744 writes data to a \fBBIO_s_dgram_pair\fR\|(3) or otherwise takes action so that the
745 QUIC implementation can read new datagrams via a call to \fBBIO_recvmmsg\fR\|(3) on
746 the underlying network BIO. The QUIC implementation may output datagrams via a
747 call to \fBBIO_sendmmsg\fR\|(3) and the application is responsible for ensuring these
750 The application must call \fBSSL_get_event_timeout\fR\|(3) after every call to
751 \&\fBSSL_handle_events\fR\|(3) (or another I/O function on the SSL object), and ensure
752 that a call to \fBSSL_handle_events\fR\|(3) is performed after the specified timeout
756 \&\fBSSL_handle_events\fR\|(3), \fBSSL_get_event_timeout\fR\|(3),
757 \&\fBSSL_net_read_desired\fR\|(3), \fBSSL_net_write_desired\fR\|(3),
758 \&\fBSSL_get_rpoll_descriptor\fR\|(3), \fBSSL_get_wpoll_descriptor\fR\|(3),
759 \&\fBSSL_set_blocking_mode\fR\|(3), \fBSSL_shutdown_ex\fR\|(3),
760 \&\fBSSL_set1_initial_peer_addr\fR\|(3), \fBSSL_stream_conclude\fR\|(3),
761 \&\fBSSL_stream_reset\fR\|(3), \fBSSL_get_stream_read_state\fR\|(3),
762 \&\fBSSL_get_stream_read_error_code\fR\|(3), \fBSSL_get_conn_close_info\fR\|(3),
763 \&\fBSSL_get0_connection\fR\|(3), \fBSSL_get_stream_type\fR\|(3), \fBSSL_get_stream_id\fR\|(3),
764 \&\fBSSL_new_stream\fR\|(3), \fBSSL_accept_stream\fR\|(3),
765 \&\fBSSL_set_incoming_stream_policy\fR\|(3), \fBSSL_set_default_stream_mode\fR\|(3),
766 \&\fBSSL_new_listener\fR\|(3), \fBSSL_new_listener_from\fR\|(3), \fBSSL_is_listener\fR\|(3),
767 \&\fBSSL_get0_listener\fR\|(3), \fBSSL_listen\fR\|(3), \fBSSL_accept_connection\fR\|(3),
768 \&\fBSSL_get_accept_connection_queue_len\fR\|(3), \fBSSL_new_domain\fR\|(3),
769 \&\fBSSL_is_domain\fR\|(3), \fBSSL_get0_domain\fR\|(3)
775 this file except in compliance with the License.  You can obtain a copy