2 ms·
Commenters seem to be convinced the school is filtering on SNI. That could be true. Based on past replies I have received, some HN commenters also believe tha
by 1vuio0pswjnm7 2y ago
Commenters seem to be convinced the school is filtering on SNI. That could be true. Based on past replies I have received, some HN commenters also believe that the entire web requires SNI. This is not true.
For example, the website hrw.org cited by the OP does not require SNI. The following request succeeds:
printf 'GET / HTTP/1.1\r\nHost: www.hrw.org\r\nConnection: close\r\n\r\n' \
|openssl s_client -connect 23.185.0.2:443 -ign_eof -noservername
Unfortunately so-called "modern" browsers disregard this fact and the implications of SNI on web users. They send SNI to every website, irrespective of whether it is required or not. One CDN may offer ECH to encrypt SNI if TLS1.3 is used and the client supports ECH. But one CDN is not the entire web. Needless to say, hrw.org is not using this CDN.
Personally I use clients that do not send SNI by default and localhost-bound forward proxies that allow me to enable or disable sending SNI for any given website.
Interesting that a student would be familiar with "MITM" and "DoH" but oblivious to SNI. SNI predates and defeats any alleged "DNS privacy" of DoH. No MITM needed.
Another test would be to run a local DoH proxy, e.g., AdGuard's "dnsproxy". This way one can avoid the remote certificate check that the so-called "modern" browser is probably trying to perform periodically when using DoH. The computer owner can serve their own self-signed certificate.