5 ms·
"But SNI breaks down for apps that don't use TLS, and we want to support all kinds of apps, not just web apps." SNI is nothing but a PITA for users who don't w
by 1vuio0pswjnm7 5y ago
"But SNI breaks down for apps that don't use TLS, and we want to support all kinds of apps, not just web apps."
SNI is nothing but a PITA for users who don't want to send Host headers in plaintext over the wire.
It may be a small number of users who are aware of the SNI leak, but it doesn't mean they are being unreasonable for wanting to plug it.
https://curvecp.org/addressing.html https://curvecp.org/addressing.html
"An ISP or site administrator can easily run a huge number of CurveCP servers on a single global IPv4 address, even if the servers are independently operated with separate long-term public keys. This feature is provided by a simple extension mechanism in CurveCP addresses.
CurveCP servers are inherently anti-aliased, providing automatic virtual hosting and fixing some of the deficiencies in the "same-origin" policy in web browsers. This feature is provided by a simple domain-name mechanism in CurveCP addresses.
If a site has two server addresses, and one server is down, a CurveCP client will quickly connect to the other address.
A CurveCP connection remains fully functional even if the client changes IP address.
CurveCP is fully compatible with existing NAT (network address translation) mechanisms; none of the above features require clients or servers to know the global addresses of their gateways."
I will keep using CurveCP forwarders on the home LAN because I like it and just in case it ever sees interest from a wider audience, like Curve25519 eventually did. No expectations.
- hamandcheese 5y agoIf a site doesn't use SNI, therefore serves no more than one HTTPS site from any single IP, don't you still leak the same amount of information simply from connecting to that IP on port 443?
- 1vuio0pswjnm7 5y agoNo. SNI sends more information. It sends a "servername" in the ClientHello. With earlier TLS versions the host could also be leaked in the server certificate that is sent to the client to be verified. With TLS1.3 that is fixed. All that remains is to plug the SNI leak. Experimental encrypted ClientHello is available, but not in popular graphical browsers. Popular graphical browsers send a servername in the ClienHello even when SNI is not required! (Most HTTPS site submitted to HN do not require SNI.) To see how SNI leaks host names, https://github.com/kontaxis/snidump https://github.com/kontaxis/snidump # example.com - with no SNI echo -e "GET / HTTP/1.1\r\nHost: example.com\r\nConnection: close\r\n\r\n"|openssl s_client -connect example.com:443 -ign_eof -noservername # example.org - with SNI echo -e "GET / HTTP/1.1\r\nHost: example.org\r\nConnection: close\r\n\r\n"|openssl s_client -connect example.org:443 -ign_eof -servername example.org You should see "example.org" in the snidump output. Neither the example.com nor the example.org sites require SNI.
- johncolanduoni 5y agoBut since there’s no ability to share IPs between different sites without SNI, haven’t you just made things easier for censors/snoops? Instead of having to sessionize TCP and decode TLS, they can get everything they need with stateless L3 monitoring.
- deleted 5y ago[deleted]