Lines Matching refs:connection

162      TLS 1.3 connection potentially resulting in a Denial of Service or forced
172        was able to successfully establish a TLS 1.2 connection with the server.
223    * Fix the restoration of the ALPN when loading serialized connection with
1067    * Add the function mbedtls_ssl_get_own_cid() to access our own connection id
1227    * Fix server connection identifier setting for outgoing encrypted records
1229      connection identifier, the Mbed TLS client now properly sends the server
1230      connection identifier in encrypted record headers. Fix #5872.
1331      to select the 1.3 version of the protocol to establish a TLS connection.
1339      man-in-the-middle to inject fake ciphertext into a DTLS connection.
1589      context are now connection-specific.
2394      when receiving a connection with CID, when these fields were shifted
2783      in https://tools.ietf.org/html/draft-ietf-tls-dtls-connection-id-05.
2785      lifetime of the underlying transport by adding a connection identifier
2787      incoming record with the correct connection data even after the peer has
3177      with the peer, as well as by a new per-connection MTU option, set using
3240      this recovery by sending many messages in the same connection. With TLS
3310      to the connection being terminated. Seen most often with OpenSSL using
3516      that when both sides of a TLS connection negotiate the truncated
3527      HMAC key of a single, uninterrupted connection (with no
3916      sending the fatal alert and just drop the connection.
4302      connection, if cookie verification is available
5615    * Added ssl_session_reset() to allow better multi-connection pools of
5616      SSL contexts without needing to set all non-connection-specific
5764      to negotiate anonymous connection (Fixes ticket #12,
5838      connection.