Lines Matching full:tls

13 some OpenSSL and TLS fundamentals (see L<ossl-guide-libraries-introduction(7)>
14 and L<ossl-guide-tls-introduction(7)>).
21 TLS protocol for connection establishment but independently protects packets.
22 It provides similar security guarantees to TLS such as confidentiality,
23 integrity and authentication (see L<ossl-guide-tls-introduction(7)>).
38 client and server as is required when opening an additional TLS/TCP
50 transmitted without any waiting time. This is similar to TLS 1.3's 0-RTT
52 it is similar to a combination of TLS 1.3 0-RTT and TCP Fast Open.
62 allowing support for both TLS and DTLS-style use cases on a single connection.
82 A key difference between the TLS implementation and the QUIC implementation in
106 =head1 QUIC AND TLS
108 QUIC reuses parts of the TLS protocol in its implementation. Specifically the
109 TLS handshake also exists in QUIC. The TLS handshake messages are wrapped up in
110 QUIC protocol messages in order to send them to the peer. Once the TLS handshake
112 without using TLS - although some TLS handshake messages may still be sent in
115 This relationship between QUIC and TLS means that many of the API functions in
116 OpenSSL that apply to TLS connections also apply to QUIC connections and
121 to both TLS and QUIC.
128 without any loss of data or reordering of the bytes. A TLS application
129 effectively has one bi-directional stream available to it per TLS connection. A
148 TLS assumes "stream" type semantics for its underlying transport layer protocol
155 A significant difference between OpenSSL TLS applications and OpenSSL QUIC
156 applications is the way that blocking is implemented. In TLS if your application
180 L<ossl-guide-libssl-introduction(7)>, L<ossl-guide-tls-introduction(7)>,
181 L<ossl-guide-tls-client-block(7)>, L<ossl-guide-quic-client-block(7)>,