What If Netscape Did SSL the HTTP Way?

6 points by cript0nauta


hanno

Just want to point out that "connect in plaintext first, then upgrade" is a recipe for security vulnerabilities. If you want to know how that looks, just look at STARTTLS (I co-authored that paper): https://nostarttls.secvuln.info/

The HTTP-upgrade-to-TLS thing mentioned (RFC 2817) that is still implemented by some obscure HTTP servers is also flawed: https://opossum-attack.com/

fanf

It’s a mistake to push TLS up the stack: it’s much better to move the security layer as low as possible (like QUIC) so that it can secure the transport, and so that different application protocols can share the security layer. TLS has been very good at application neutrality: basically only ssh has its own security layer and that’s largely due to it being too early.

Another interesting parallel universe is one in which IPSEC had been usable by applications without cooperation from the kernel, and supported single-end authentication with a PKI. (I don’t know enough about IPSEC’s key distribution and authentication model, but I guess that’s another reason it’s only used in VPNs.)

ryan-duve

they can’t make one that’s valid for shop.example.com without a CA’s help, and if they can get one of those, you have bigger problems.

I used to share this stance before eMudhra.

adrien

The premise seemed interesting to me but the page is completely AI-generated unfortunately.