4 ms·
Hey, hey, what's with the "..." and cutting out the relevant parts? I explicitly mention SSL and TLS. Those are encryption standards that are designed exclusive
by maratd 14y ago
Hey, hey, what's with the "..." and cutting out the relevant parts? I explicitly mention SSL and TLS. Those are encryption standards that are designed exclusively for privacy.
If I am using them to communicate with a 3rd party, I have a reasonable expectation of privacy between myself and that 3rd party. You would most certainly need a warrant to turn around and try to get access to a message stored on their servers.
On top of that, quite a bit of email today doesn't even touch SMTP. If I'm sending an email from one GMail user to another GMail user, I'm pretty sure it is just shuffled around on Google's internal servers. And, of course, I'm connecting to Google using SSL, an encrypted connection.
How does that not scream private?
- sliverstorm 14y agoHey, hey, what's with the "..." and cutting out the relevant parts? I explicitly mention SSL and TLS. Those are encryption standards that are designed exclusively for privacy. I cut out the SSL and TLS because I don't disagree; SSL and TLS certainly says "privacy". I wanted to specifically address the notion that "authentication =~ privacy"