3 ms·
Because it is important that everyone understand that SSL is dead and TLS is the replacement. SSL/TLS is forgivable, saying SSL is sort of like writing a headl
by parasubvert 9y ago
Because it is important that everyone understand that SSL is dead and TLS is the replacement. SSL/TLS is forgivable, saying SSL is sort of like writing a headline “How this company uses VHS” when you actually meant Betamax. It’s misleading.
- vog 9y agoI still don't get it. This is clarified in the very first sentence of TFA. Why do you think it needs to be stuffed into the title?
- mcny 9y agoWe wouldn't need to have this conversation if the title said TLS.
- nailer 9y agoYou're correct, but you're fighting an uphill battle: https://certsimple.com/blog/ssl-or-tls https://certsimple.com/blog/ssl-or-tls
- stronglikedan 9y agoWhen talking to management, I try to avoid the acronyms (SSL, TLS, HTTPS, etc.), and in this case, I've coined a phrase that I find be equally understood by management, devops, and sysadmins alike. I tell them that we need to "encrypt server X with a secure certificate" (or "secure cert" depending who I'm talking to, which is as short as the shortest acronym syllable-wise). It's vague enough to cover the spectrum of acronyms in a timeless (for the foreseeable future) way, but unambiguous enough that everyone understands.
- deleted 9y ago[deleted]