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

Memes

45704 readers
1314 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 88 points 7 months ago (23 children)

The ISP can see every domain, but not every page. That's what HTTPS everywhere was all about.

[–] bjoern_tantau@swg-empire.de 15 points 7 months ago (10 children)

And hopefully in the future they won't even he able to see the domain. I wonder why they never considered giving out certificates for IPs to solve this problem. Seemed like the easiest solution to me.

[–] magic_lobster_party@kbin.run 18 points 7 months ago (1 children)

They need the IP address to know where to forward the packet to. Hard to avoid that without VPN or TOR.

[–] JDubbleu@programming.dev 2 points 7 months ago

There was a demo for a technology put out recently that circumvents this. I don't remember the exact mechanisms, but it obscured DNS such that your ISP couldn't see the DNS record you requested, and then used a proxy to route traffic before it hit the final endpoint eliminating exposing the IP to your ISP. It worked very similar to a VPN, but without the encrypted connection, and had some speed focused optimizations including the proxy being proximate to your ISP. It was pretty interesting.

load more comments (8 replies)
load more comments (20 replies)