Lines Matching full:tls

71 some OpenSSL and TLS fundamentals (see \fBossl\-guide\-libraries\-introduction\fR\|(7)
72 and \fBossl\-guide\-tls\-introduction\fR\|(7)).
79 It provides similar security guarantees to TLS such as confidentiality,
80 integrity and authentication (see \fBossl\-guide\-tls\-introduction\fR\|(7)).
92 client and server as is required when opening an additional TLS/TCP
102 transmitted without any waiting time. This is similar to TLS 1.3's 0\-RTT
104 it is similar to a combination of TLS 1.3 0\-RTT and TCP Fast Open.
112 allowing support for both TLS and DTLS-style use cases on a single connection.
127 A key difference between the TLS implementation and the QUIC implementation in
150 .SH "QUIC AND TLS"
151 .IX Header "QUIC AND TLS"
152 QUIC reuses parts of the TLS protocol in its implementation. Specifically the
153 TLS handshake also exists in QUIC. The TLS handshake messages are wrapped up in
154 QUIC protocol messages in order to send them to the peer. Once the TLS handshake
156 without using TLS \- although some TLS handshake messages may still be sent in
159 This relationship between QUIC and TLS means that many of the API functions in
160 OpenSSL that apply to TLS connections also apply to QUIC connections and
165 to both TLS and QUIC.
171 without any loss of data or reordering of the bytes. A TLS application
172 effectively has one bi-directional stream available to it per TLS connection. A
197 A significant difference between OpenSSL TLS applications and OpenSSL QUIC
198 applications is the way that blocking is implemented. In TLS if your application
220 \&\fBossl\-guide\-libssl\-introduction\fR\|(7), \fBossl\-guide\-tls\-introduction\fR\|(7),
221 \&\fBossl\-guide\-tls\-client\-block\fR\|(7), \fBossl\-guide\-quic\-client\-block\fR\|(7),