{"id":41310209,"user":"udev4096","time":1724247799,"time_ago":"a year ago","type":"comment","content":"

Good to see phrack finally supporting HTTPS.","comments":[{"id":41311426,"user":"throw_pm23","time":1724255497,"time_ago":"a year ago","type":"comment","content":"

Seriously, who cares, it is an essay in a text file.","comments":[{"id":41314985,"user":"brunoqc","time":1724280923,"time_ago":"a year ago","type":"comment","content":"

because your ISP doesn't need to know what your read?","comments":[{"id":41315455,"user":"saagarjha","time":1724285588,"time_ago":"a year ago","type":"comment","content":"

I have bad news to share about how DNS works","comments":[{"id":41315909,"user":"brunoqc","time":1724290950,"time_ago":"a year ago","type":"comment","content":"

It seems a bit presumptive to assume I’m unfamiliar with how DNS works. While it’s true that DNS traffic to your ISP is generally readable, using HTTPS still offers significant privacy benefits. A single domain, like twitter.com, can transmit a vast amount of data. Additionally, with the ease of obtaining a free SSL certificate these days, neglecting to implement one could be considered careless.","comments":[{"id":41325169,"user":"saagarjha","time":1724369811,"time_ago":"a year ago","type":"comment","content":"

I’m going to reply to both you and your sibling comment because they’re basically the same from the perspective of what I wanted to say: just because you know some stuff about DNS isn’t actually enough, because there’s a wider context that you’re missing. Most importantly, without a VPN the traffic you send will often go to an IP that is controlled by a single entity, so your ISP is going to route packets from you to [Phrack IP]. Of course the content of those packets is going to be encrypted, but it doesn’t take a genius to figure out that everyone is reading Phrack 71 that just came out. So that’s basically enough to figure out everything already. But to bring it back to DNS even then it’s riddled with issues as you’re aware of: it’s complete unencrypted by default, so that just gives you the domain directly. Often you’re going to be sending that traffic to your ISP directly but even if you’ve set things up to use a different server you still haven’t solved the problem of people being able to know what you’re doing.","comments":[{"id":41326565,"user":"udev4096","time":1724394344,"time_ago":"a year ago","type":"comment","content":"

Of course, the IP is visible. It's quite obvious. Most of the third party upstream DNS supports DoH, so the only thing your ISP will get is the queries of your requests to the DNS provider","comments":[],"comments_count":0,"level":5,"url":"item?id=41326565"}],"comments_count":1,"level":4,"url":"item?id=41325169"}],"comments_count":2,"level":3,"url":"item?id=41315909"},{"id":41318496,"user":"udev4096","time":1724321134,"time_ago":"a year ago","type":"comment","content":"

And who said everyone uses ISP's upstream DNS? Please stop assuming","comments":[{"id":41325176,"user":"saagarjha","time":1724370008,"time_ago":"a year ago","type":"comment","content":"

Uh, nobody? It’s not relevant.","comments":[],"comments_count":0,"level":4,"url":"item?id=41325176"}],"comments_count":1,"level":3,"url":"item?id=41318496"},{"id":41350986,"user":"RGBCube","time":1724617129,"time_ago":"a year ago","type":"comment","content":"

I have good news to share about how DNS over HTTPS, archive.is and/or Tor works.","comments":[],"comments_count":0,"level":3,"url":"item?id=41350986"}],"comments_count":6,"level":2,"url":"item?id=41315455"}],"comments_count":7,"level":1,"url":"item?id=41314985"}],"comments_count":8,"level":0,"url":"item?id=41311426"}],"comments_count":9,"url":"item?id=41310209"}

Comment by udev4096