Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why SSL was renamed to TLS in late 90s (2014)

tim.dierks.org

Post reply on HN
Print view View original

231–237 of 237 posts

Re: Why SSL was renamed to TLS in late 90s (2014)

#231

Post by albert_e »

cubes wrote: post #193
albert_e wrote: post #21

Related Randomness and the Netscape Browser January 1996 Dr. Dobb's Journal https://people.eecs.berkeley.edu/~daw/papers/ddj-netscape.ht... This was written in 1996. The language used feels already much different from today's publications. God I feel old.

The authors of that article got pictured on the cover of the New York Times for finding that security issue: https://www.nytimes.com/2012/02/15/technology/researchers-fi...

Interesting link - thanks.

Was it the same issue though --

the Netscape SSL issue is from year 1996.

The linked NYT article is about vulnerability with public key encryption dated 2012 by different authors.

Re: Why SSL was renamed to TLS in late 90s (2014)

#232

Post by LukeShu »

aoetalks wrote: post #150
LukeShu wrote: post #41

Earlier quoted context omitted.

No? The "transport" layer is layer 4 in the 7-layer OSI model (physical/datalink/network/transport/session/presentation/application) and 5-layer IP model (physical/network/internetwork/transport/application). That is: the "transport" provides reliable continuous data-stream abstraction over the lower-layers' discreet and unreliable packets; e.g. TCP. And that data-stream the interface that TLS provides; to the higher…

I was about to agree with you, and then I read the article on DTLS. > And that data-stream the interface that TLS provides That’s exactly the problem. You might lose a UDP packet. That would corrupt data encrypted with stream cipher. With DTLS, each packet is encrypted individually. https://en.m.wikipedia.org/wiki/Datagram_Transport_Layer_Sec...

I would agree with you that DTLS is a misnomer; that it does not provide the layer-4/transport-layer -like interface that regular TLS provides.

(It isn't quite a layer-3/internetwork-layer -like interface; from the UDP that it sits on, it has a multiplexing component that is "half" of a layer 4 interface.)

Re: Why SSL was renamed to TLS in late 90s (2014)

#233

Post by notpushkin »

twodave wrote: post #201
eptcyka wrote: post #118

Earlier quoted context omitted.

Never not been appropriate.

Yeah, it’s just that Googl€, A₽₽le, etc. have all caught up with them. If they’re all the same then there’s less of a need to differentiate anymore.

A₽₱le!

Re: Why SSL was renamed to TLS in late 90s (2014)

#234

Post by strawhatguy »

dylan604 wrote: post #214
unaindz wrote: post #213

Earlier quoted context omitted.

I agree with all except your example. TLS and SSL are about the same memorability wise, Twitter and X are not. If we were talking about a porn website it would be the inverse.

The fact that they still refer to them as tweets is another thing. What would they call them instead, exes? Those are best kept in Texas.

That’s the big thing for me. Twitter had its own name for posts. I think it is just posts now.

Re: Why SSL was renamed to TLS in late 90s (2014)

#235

Post by Sophira »

happyopossum wrote: post #200
vladvasiliu wrote: post #192

Earlier quoted context omitted.

Many servers and clients support both ipv4 and ipv6. So, in a sense, there's a "negotiation" happening between client and server.

That’s not negotiating- I can’t connect to a server over v4 and have it tell me to switch to v6 or vice versa. That’s just supporting 2 completely different protocols.

Right. The closest thing we have to IPv6 "negotiation" is the Happy Eyeballs algorithm[0], which is literally just "connect to both at the same time and pick the one that connects first". The name serves to legitimise it and make it sound fancy but it's basically just brute force + a bit of caching.

[0] https://en.wikipedia.org/wiki/Happy_Eyeballs

Re: Why SSL was renamed to TLS in late 90s (2014)

#237

Post by ItsHarper »

throwaway843 wrote: post #196
slt2021 wrote: post #82

Earlier quoted context omitted.

SSL is used in websites. TlS is used in other applications, as in mTLS

Unfortunately you were voted down for answering OP. SSL for websies, TLS for email, tunnels, XMPP, etc.

TLS is used for websites too.
Post reply on HN