Re:Privacy activists oppose EU plans for a GDPR-compliant Wh...
by dathinab on Saturday October 16, 2021 @08:44PM
(#28892969)
You are totally overthinking things.
1. This affects http, too. I mean it affects anything using domains names.
2. It's generally a bad argument as there are so many more ways state agencies can mess with you when you use http then when you use https.
3. did you read the article? (I guess no)
4. The problem is DNS and DNS only, everything else is just a side effect from DNS being conceptually broken (wrt. privacy protection and decentralization). Https everywhere is inevitable and good, what isn't is that due to how DNS works we ended up with a (kinda) centralized-only certificate system. Https happens to need certificates, but it doesn't care what system provides them for it. So a complete privacy preserving decentralized certificate (and DNS replacement) could totally work with HTTPS.
1. This affects http, too. I mean it affects anything using domains names.
2. It's generally a bad argument as there are so many more ways state agencies can mess with you when you use http then when you use https.
3. did you read the article? (I guess no)
4. The problem is DNS and DNS only, everything else is just a side effect from DNS being conceptually broken (wrt. privacy protection and decentralization). Https everywhere is inevitable and good, what isn't is that due to how DNS works we ended up with a (kinda) centralized-only certificate system. Https happens to need certificates, but it doesn't care what system provides them for it. So a complete privacy preserving decentralized certificate (and DNS replacement) could totally work with HTTPS.