STOP SAYING
SSL.
Nobody has used SSL since 2015. Your “SSL certificate” is an X.509 certificate. Your “SSL port” is 443, which has no opinion. It has all been TLS the whole time.
⚠ 1 protocol is not responding
Type the name of a program, folder, or document.
POODLE broke SSL 3.0 on 14 October 2014. RFC 7568 deprecated it the following June.
| compiling… |
Paste something you wrote this week.
A dollar a go, purely for fun. “SSL 2.0” and “SSL 3.0” are free, those are their actual names.
“But the command is literally called openssl.”
Correct. nginx also says ssl_certificate, Apache still ships
mod_ssl, and your load balancer sells you “SSL offload”.
Every one of them is speaking TLS. Those names just never got updated.
“Everyone knows what I mean.”
They do. Names are sticky, though. SSLv3 stayed switched on in production for fifteen years after TLS replaced it.
“Your domain is called fuckssl.com.”
Yes. Nobody would have typed fucktls.com.
“So what do I say?”
TLS. TLS certificate. TLS termination. TLS 1.3 if you want the good one (RFC 8446), TLS 1.2 if you have to support a fridge.
“Is this actually a big deal?”
Not really. But names are how people find things, and SSL points at nothing now. TLS is the same number of syllables.
This page ships roughly 1.3 MB of language compilers in order to deliver one word.
- LiveScript 1.6.1
- compiled to JavaScript in your browser, just now
- prelude.ls 1.2.1
- because
|> - Scittle 0.6.22
- ClojureScript, also compiled in your browser, also just now
- Reagent
- the swear jar is a React app
- Blueprint CSS 1.0.1
- a grid framework from 2007
- 98.css
- the window chrome
Served over TLS 1.3.
| reading… |
The HTML standard requires every one of those, so code from 1998 keeps working. The names stayed put long after the things behind them went.
