this post was submitted on 23 Apr 2024
1050 points (97.0% liked)

Memes

45727 readers
1090 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] mipadaitu@lemmy.world 5 points 7 months ago (7 children)

That solves a completely different problem. The ISP can still see who you requested data from.

That's more about security around retrieving the correct IP address from a DNS query, and doesn't do that much for privacy.

[–] ShortN0te@lemmy.ml 5 points 7 months ago (6 children)

DoT also encrypts the request, so the ISP cannot spy on the Domain Name you have requested.

And thanks to Https the ISP only sees the IP address which cannot in every case be resolved to a unique Domain, especially large sites that are hosted on service providers like Cloudflare, amazon etc etc

[–] Darkassassin07@lemmy.ca 2 points 7 months ago* (last edited 7 months ago) (5 children)

But what's not encrypted by either is the Server Name Indicator or SNI, ie: the initial request to a webserver stating which host you're trying to reach at that IP, before establishing the TLS connection, contains the domain you'd requested via DoH/DoT, in plaintext.

[–] Album@lemmy.ca 3 points 7 months ago (1 children)

encrypted SNI is a thing now.

[–] Darkassassin07@lemmy.ca 4 points 7 months ago

True. Known as Encrypted Client Hello now, as part of TLS1.3.

It seems many more browsers support it than last I'd looked. I'm curious to see how much of the general web has adopted support for it onnthe server side. I'll have to look into that more, and see what it'll take to setup for self-hosting.

load more comments (3 replies)
load more comments (3 replies)
load more comments (3 replies)