Lines Matching refs:object
12 A QUIC-TLS handshake is managed by a QUIC_TLS object. This object provides
19 The `ossl_quic_tls_new` function instantiates a new `QUIC_TLS` object associated
26 A key field of the `args` structure is the `SSL` object (`s`). This "inner"
27 `SSL` object is initialised with an `SSL_CONNECTION` to represent the TLS
28 handshake state. This is a different `SSL` object to the "user" visible `SSL`
29 object which contains a `QUIC_CONNECTION`, i.e. the user visible `SSL` object
30 contains a `QUIC_CONNECTION` which contains the inner `SSL` object which
37 When the QUIC Connection no longer needs the handshake object it can be freed
52 A `QUIC_TLS_ARGS` object is passed to the `ossl_quic_tls_new` function by the
59 * The "inner" SSL object for the QUIC Connection. Contains an
114 * exceed the lifetime of the QUIC_TLS object.
130 record. QUIC handles this differently and so the QUIC_TLS object will intercept
134 parameters". These transport parameters are opaque to the `QUIC_TLS` object. It
144 The `QUIC_TLS` object utilises two main mechanisms for fulfilling its functions:
151 A TLS record layer is defined via an `OSSL_RECORD_METHOD` object. This object
183 `QUIC_TLS` object are:
187 Invoked every time a new record layer object is created by the TLS
217 when `crypto_recv_cb` is invoked the data is copied into a QUIC_TLS object
241 not been set then the `QUIC_TLS` object immediately fails.
246 related data in the `SSL` object. Public API functions that are only relevant to
255 TLSv1.3 is used as a minimum. Therefore the `QUIC_TLS` object automatically
260 normal TLS this is "on" by default. Therefore the `QUIC_TLS` object will
