Why SSL was renamed to TLS in late 90s (2014)
11–20 of 237 posts
Re: Why SSL was renamed to TLS in late 90s (2014)
#12“Transport Layer Security” really is a better name though. I also like to say “TLS”. Two Ses in a row makes you sound like a snake.
Transport Layer Security is widely documented as beginning in 1999.
I can find references to "Thread Local Storage" going back to at least 1996. That particular term seems more common in the Microsoft (and maybe IBM, does anyone have an OS/2 programming manual?) world at the time; Pthreads (1995) and Unix in general tended to call it "thread-specific data".
It's possible that the highly influential 2001 Itanium ABI document (which directly led to Drepper's TLS paper) brought the term to (widespread) use in the broader Unix world, though Sun (for both Solaris and Java?) was using the term previously. But it's also possible that I'm just missing the reference material.
Re: Why SSL was renamed to TLS in late 90s (2014)
#13tl;dr: politics. I still like to occasionally refer to TLS 1.3 as "SSL 3.4" to see whether people are aware of the history.
Re: Why SSL was renamed to TLS in late 90s (2014)
#14“Transport Layer Security” really is a better name though. I also like to say “TLS”. Two Ses in a row makes you sound like a snake.
The problem is that TLS was already in widespread use for "thread local storage". Transport Layer Security is widely documented as beginning in 1999. I can find references to "Thread Local Storage" going back to at least 1996. That particular term seems more common in the Microsoft (and maybe IBM, does anyone have an OS/2 programming manual?) world at the time; Pthreads (1995) and Unix in general tended to call it "t…
Re: Why SSL was renamed to TLS in late 90s (2014)
#15> As a part of the cutthroat competition, Microsoft decided to revise the SSL 2 protocol with some additions of their own, and specified a protocol called "PCT" that was derived from SSL 2. It was only supported in IE and IIS. > Netscape also wanted to address SSL 2 issues, but wasn't going to let Microsoft take leadership/ownership in the standard, so they developed SSL 3.0, which was a more significant departure. I…
Two decades later, and it is still common for people to call TLS SSL.
Re: Why SSL was renamed to TLS in late 90s (2014)
#16“Transport Layer Security” really is a better name though. I also like to say “TLS”. Two Ses in a row makes you sound like a snake.
Re: Why SSL was renamed to TLS in late 90s (2014)
#17Oh wow, I just discovered that my brain unconsciously had a hard time to differentiate between SSL and TLS. And now, after two friggin decades I find out, why!
Re: Why SSL was renamed to TLS in late 90s (2014)
#18Re: Why SSL was renamed to TLS in late 90s (2014)
#19“Transport Layer Security” really is a better name though. I also like to say “TLS”. Two Ses in a row makes you sound like a snake.
The problem is that TLS was already in widespread use for "thread local storage". Transport Layer Security is widely documented as beginning in 1999. I can find references to "Thread Local Storage" going back to at least 1996. That particular term seems more common in the Microsoft (and maybe IBM, does anyone have an OS/2 programming manual?) world at the time; Pthreads (1995) and Unix in general tended to call it "t…
Look to Windows NT rather than to OS/2 for thread-local storage. TlsAlloc() et al. were in the Win32 API right from NT 3.1, I think.