= 27d567bc2d48d9f40e9ccc20ea370b15)
DanielLC comments on Procedural knowledge gap: public key encryption - Less Wrong Discussion
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (18)
You only have to configure it because it isn't standard. If it was, anyone who had a mail client would be able to read it.
I don't just mean email. I was referring to any kind of information transfer.
What's especially odd is with webpages. I've never seen a browser that can't handle https, and yet, if you're not sending something secure, they just use http.
But an HTTP server that doesn't have a unique IP address cannot use HTTPS. There are extensions to the standard that fix this problem (e.g., Server Name Indication), but they are not widely supported. (The problem stems from SSL working on a lower level of abstraction than HTTP.)