Lines Matching +full:use +full:- +full:handshake

1 QUIC-TLS Handshake Integration
4 QUIC reuses the TLS handshake for the establishment of keys. It does not use
6 confidentiality and integrity of QUIC packets itself. Only the TLS handshake is
10 ---------------
12 A QUIC-TLS handshake is managed by a QUIC_TLS object. This object provides
22 various key points during the handshake lifecycle such as when new keys are
24 handshake is complete.
28 handshake state. This is a different `SSL` object to the "user" visible `SSL`
37 When the QUIC Connection no longer needs the handshake object it can be freed
45 state of the QUIC-TLS handshake. On each call to `ossl_quic_tls_tick` newly
50 -------------
65      * Called to send data on the crypto stream. We use a callback rather than
87      * Note: These parameters are not authenticated until the handshake is
96      * Called when the handshake has been completed as far as the handshake
105      * handshake layer is concerned, meaning that it should be immediately torn
122 QUIC-TLS handshake when there is new CRYPTO frame data to be sent, or when it
125 When the TLS handshake generates secrets they will be communicated to the
126 OpenSSL QUIC implementation via the `yield_secret_cb`, and when the handshake
129 In the event that an error occurs a normal TLS handshake would send a TLS alert
133 QUIC requires the use of a TLS extension in order to send and receive "transport
135 does not need to use them directly but instead simply includes them in an
142 -----------------------
168 to first check whether a custom record method has been specified and always use
177 Existing TLS record layers use TLS keys and IVs that are calculated using a
179 higher level secret as well as the digest to be used in the KDF - so these
194 Invoked every time the TLS implementation wants to send TLS handshake data. This
208 Invoked when the TLS implementation wants to read more handshake data. This
237 QUIC requires the use of ALPN (Application-Layer Protocol Negotiation). This is
240 `SSL_set_alpn_protos` prior to initiating the handshake. If the ALPN data has
245 The `SSL_CONNECTION` used for the TLS handshake is held alongside the QUIC
252 configured just before the handshake starts.