Lines Matching refs:record
5 the standard TLS record layer and instead assumes responsibility for the
130 record. QUIC handles this differently and so the QUIC_TLS object will intercept
146 * It registers itself as a custom TLS record layer
151 A TLS record layer is defined via an `OSSL_RECORD_METHOD` object. This object
153 record layer. Existing record layers include one for TLS, one for DTLS and one
156 `QUIC_TLS` registers itself as a custom TLS record layer. A new internal
157 function is used to provide the custom record method data and associate it with
167 implementation to work out which record method should be used next is modified
168 to first check whether a custom record method has been specified and always use
171 The TLS record layer code is further modified to provide the following
174 The custom record layer will need a record layer specific argument (`rlarg`
177 Existing TLS record layers use TLS keys and IVs that are calculated using a
187 Invoked every time a new record layer object is created by the TLS
199 alert data supplied by the TLS implementation (always a 2 byte record payload)
202 alert record to be fragmented across two 1 byte records this is never done in
214 expects to request data from the record layer, get a handle on that data, and
215 then inform the record layer when it has finished using that data. The current
