3 ms·
Then you must ask the OS vendors to include it, not startup developers. And in any case, encrypting DNS won't solve the surveillance issue, since the HTTPS han
by icebraining 11y ago
Then you must ask the OS vendors to include it, not startup developers.
And in any case, encrypting DNS won't solve the surveillance issue, since the HTTPS handshake sends the domain in clear-text, so that the server knows which certificate to send (https://en.wikipedia.org/wiki/Server_Name_Indication https://en.wikipedia.org/wiki/Server_Name_Indication)
- malka 11y agoOne could use a single certificate that is valid for all domain on the server
- icebraining 11y agoThe client would still send the domain, since it doesn't known the server only has one certificate (the domain is sent in the first message, the ClientHello).
- malka 11y agooh yes very true. Had not thougth of that.