3 ms·
If bawolff knew the domain name, why did he not give that as the answer to the hypothetical. Strange. Looking up the certificate for about.censys.io on crt.sh
by 1vuio0pswjnm7 4y ago
If bawolff knew the domain name, why did he not give that as the answer to the hypothetical. Strange.
Looking up the certificate for about.censys.io on crt.sh is not the same as looking up the certificate for 185.199.108.153.
Try it. https://crt.sh/?q=185.199.108.153 https://crt.sh/?q=185.199.108.153
If starting with only an IP address, 185.199.108.153, what does the certificate reveal.
echo|openssl s_client -connect 185.199.108.153:443 -showcerts|openssl x509 -text
Does it indicate the domain name the user intended to visit, about.censys.io, as would SNI.
SNI reveals more than "Its a github page" or a list of sites that are "related", i.e., hosted on the same IP address.^1
SNI provides the network observer with the exact domain name that a user intended to visit. Aside from faking SNI, domain fronting, or similar tactics, the results are reliable.
IP addresses do not indicate the exact domain name that a user intended to visit. Methods used to try to guess the domain name are unreliable.
A list of remote IP addresses observed on the wire is not the same as a list of domain names observed on the wire as servernames (SNI).
The former requires more work than the later and produces ambiguous, unreliable results.
1. A network observer could look for Subject Alternative Names in certificates passing over the wire in cleartext and try to guess which domain name the user intended to visit. However this will not work for TLS1.3 because the certificates will be encrypted.
- bawolff 4y ago> If bawolff knew the domain name, why did he not give that as the answer to the hypothetical. Strange. You misunderstand me. My point is that there are two cases - the one where the SNI reveals something useful but you also need some sort of SNI because the server serves lots of things and needs to know which you are requesting, and the one you dont need SNI but its trivial to figure out what domain regardless. Your example is an instance of the former. You can't get rid of the SNI in this case because the web server at the other end depends on it to function. So its a bad example for your purposes because the example neccesarily depends on the SNI existing to exist. If your proposed solution of removing SNI was adopted the site would not work, so removing SNI does not increase privacy in this case as the site would neccesarily have to adjust how it works in a waythat removes any of the privacy gains. (You could probably say ESNI, but if so, its already in progress albeit slow, so i still dont see your point)