Why TLS 1.3 isn't in browsers yet

Re:Why TLS 1.3 isn't in browsers yet by lmz on Wednesday December 27, 2017 @08:24PM (#16019584)

Doesn't WebRTC have a handshake protocol to ensure that the other end expects the WebRTC media stream?

[ Parent | on HN ]

Re:Why TLS 1.3 isn't in browsers yet by banachtarski on Wednesday December 27, 2017 @09:51PM (#16019965)

If you allow a browser to open sockets to random places, it's the exact same principle! The onus is on the listener to ensure that the people communicating respect the agreed upon protocol.

[ Parent | on HN ]

Re:Why TLS 1.3 isn't in browsers yet by tokenizerrr on Wednesday December 27, 2017 @10:53PM (#16020194)

Then every browser could be used to send spam. It would be horrible. Imagine that every person who visits a compromised page immediately started sending spam emails over smtp. Or spam irc messages.

[ Parent | on HN ]

Re:Why TLS 1.3 isn't in browsers yet by roblabla on Thursday December 28, 2017 @04:21AM (#16021103)

Flash could do that, and yet I've never heard of it as a problem.

[ Parent | on HN ]

Re:Why TLS 1.3 isn't in browsers yet by jhgg on Thursday December 28, 2017 @06:14AM (#16021457)

Generally is not a problem, as Flash needs to check a file called "crossdomain.xml" that is served from the destination server, which specifies how Flash can communicate with it.

http://www.adobe.com/devnet/articles/crossdomain_policy_file...

[ Parent | on HN ]