Skip to content
IAM Insights

Explainers · Glossary

SSL

Secure Sockets Layer

Secure Sockets Layer, the encryption protocol that TLS replaced. Every SSL version is deprecated as insecure, but the name survives in everyday use for TLS certificates and connections.

In our briefings

The claim each of the newest briefings on SSL would have you leave with.

  1. The 2022 RFC 9325 requires TLS implementations to have a strategy to distrust revoked certificates. It also explains why validating a certificate and proving possession of its private key does not establish that a connection reached the intended endpoint: the application needs its hostname-validation rules. For common public-PKI uses, servers should support OCSP and OCSP stapling, but stapling alone does not stop an active attacker stripping the request. Must-staple remains an operator option that needs operational review; the revocation discussion has an explicit DANE exception.

    The 2022 TLS BCP makes peer identity and session controls part of secure deploymentBI-FIND-2022-0016

  2. RFC 6698 makes DANE fail closed for clients that follow it. A TLSA record set that DNSSEC validates as secure must be used unless local policy rules out a specific association, and if none of the usable associations matches the server's certificate the client must abort the handshake. A bogus DNSSEC answer must stop TLS from starting. Records from an insecure or indeterminate answer are unusable, and the client carries on with ordinary TLS. Hoffman and Schlyter state the cost in their operational appendix: a misconfigured record set "will effectively disable access to the TLS server for all conforming clients", and the RFC offers no gradual transition. The same matching rule stops proxies that intercept TLS, which the RFC calls SSL proxies, because the proxy's certificate will not match the record.

    DANE lets a domain vouch for its own TLS keys in DNS, and a bad record locks out every client that checksBI-FIND-2012-0009

Cited in 2 briefings

Every briefing that discusses this term, newest first.

  1. The 2022 TLS BCP makes peer identity and session controls part of secure deployment

    Article · · RFC Editor · Yaron Sheffer et al. · Nov 1, 2022

  2. DANE lets a domain vouch for its own TLS keys in DNS, and a bad record locks out every client that checks

    Article · · RFC Editor · Paul Hoffman et al. · Aug 7, 2012