3 ms·
It's been okay so far, but yes, I definitely urge everyone to PGP-encrypt their messages before adding them to the service. No matter how much encryption you pu
by StavrosK 10y ago
It's been okay so far, but yes, I definitely urge everyone to PGP-encrypt their messages before adding them to the service. No matter how much encryption you put in the model layer, the service still needs to be able to read the plaintext to send it at some point...
- hueving 10y agoThe issue is that if the service gets hacked, even sending the encrypted emails to their original targets could do lots of damage to someone...
- kbenson 10y agoSo, how do you suggest encrypting the data to be sent, while still allowing for the purpose of the service, which is to distribute the data to people later on? The best I can think of off the top of my head is a dedicated PGP key, and two DMS services, one with the data, one with the key. Otherwise you're always at least exposing the data to the DMS service.
- StavrosK 10y agoI was actually thinking more the standard model, where you encrypt the email to a person's PGP key. This only works if the other person has a PGP key, though. It's the usual security <-> convenience tradeoff, unfortunately.
- avian 10y agoConsidering the rate people are losing their private PGP keys, I wouldn't trust a message that was encrypted today to be decryptable a year from now. Everyone I know that uses PGP has lost their key at least once (including myself - I forgot to write down the passphrase for a key once it expired and I no longer used it daily to refresh my memory).