Re:Brute-forcing a macOS user’s real name from a browser usi...
by ZiiS on Friday July 14, 2023 @07:31AM
(#36722369)
Unencrypted SNI is fairly rare now.
Re:Brute-forcing a macOS user’s real name from a browser usi...
by brazzledazzle on Friday July 14, 2023 @12:25PM
(#36726189)
Yeah. I noticed even server-side software is using it less too. Kind of annoying if you use SNI inspection as part of your egress security.
Re:Brute-forcing a macOS user’s real name from a browser usi...
by inferiorhuman on Friday July 14, 2023 @07:06PM
(#36731147)
Is it? The best I could find was a bit from 2021 that showed 92 of the Alexa Top 1000 site supporting ESNI. If adoption has skyrocketed since then that's great… meanwhile Firefox is showing HN negotiated a TLS 1.2 connection with no ESNI support.
Re:Brute-forcing a macOS user’s real name from a browser usi...
by Bagged2347 on Friday July 14, 2023 @10:16AM
(#36724354)
Can you elaborate on why you'd want to opt-out of DNS over HTTPS? I was under the impression that it was useful and good for privacy, but I may be misinformed.
Re:Brute-forcing a macOS user’s real name from a browser usi...
by Eisenstein on Friday July 14, 2023 @11:27AM
(#36725380)
It breaks DNS based blocking if you have it setup. Some people setup ad-blocking so that it encompasses their entire network and the way this works is that it silently drops DNS requests to ad domains on the edge of your local network.
Re:Brute-forcing a macOS user’s real name from a browser usi...
by rovr138 on Friday July 14, 2023 @11:59AM
(#36725831)
I have a local DNS server to access servers and other resources on my network. DNS over HTTPS breaks this.
Re:Brute-forcing a macOS user’s real name from a browser usi...
by inferiorhuman on Friday July 14, 2023 @07:03PM
(#36731121)
It doesn't actually break this but it does leak all of your local DNS queries to Cloudflare.
Besides, unencrypted SNI means that if my ISP wanted to get the hosts I was looking at, they could.