4 ms·
Sending private information is the first thing I think of--from a bunch of aspects. Secure in transit has had a bunch of different, awkward implementations. My
by pfranz 5y ago
Sending private information is the first thing I think of--from a bunch of aspects. Secure in transit has had a bunch of different, awkward implementations. My biggest concern is sending tax documents and it sitting in someone's archive folder (or sent folder) for years until their account is compromised.
So I often have organizations that send email pointing to their proprietary webmail. The alternative is sneakernet, hard copies, or even faxing.
- darau1 5y agoUnless you physically hand your taxes in, isn't any solution technically vulnerable to being compromised? Also, wouldn't encryption fix this problem? I don't understand how it might be implemented in the real world, but if you encrypt with your private key, then their public key the message should be safe in transit, and at rest (unless they leave it decrypted on disk)
- pfranz 5y ago> Unless you physically hand your taxes in, isn't any solution technically vulnerable to being compromised? If that's all there is to it, then why do people use other solutions? > Also, wouldn't encryption fix this problem? Kind of. The problem is the protocol and lack of consensus prevents this from being feasibly implemented. Personally, I think encryption in transit is a low probability threat for me. I would also like certain data to "expire" or go into "cold storage" after a period of time. Sending it in a side-channel, like Dropbox or Google Drive means I can delete it or revoke access after a period of time but this breaks email.