3 ms·
I've been using this. It's pretty good but - like all PGP implementations - it's really hard to use casually. You really need to make an effort to ensure you'
by edent 12y ago
I've been using this. It's pretty good but - like all PGP implementations - it's really hard to use casually.
You really need to make an effort to ensure you've got the right keys, that you can remember your password, that you know how to generate a keypair and which part of it you upload to the app.
But, once done, it works pretty well. The main downsides for me were....
- Doesn't encrypt the subject line. You don't want to say "Top Secret Docs" in there, sure, but it does make looking through mail pretty hard. Which leads to...
- No search. I pretty much rely on search to find emails. I just hadn't anticipated how much of a drag it would be to only search via sender.
- SkyMarshal 12y agoSame and /second. I'd add that I've trouble encrypting emails with attachments, as Javascript encryption performance in web-based email in a browser that's being abused with lots of other tabs open is not always so reliable. Surprise surprise. The Stanford Javascript Crypto Library whitepaper provides probably the best performance baseline for all of Javascript crypto [1], and the best they can do is roughly 10x faster than the next fastest JS crypto implementation, but still over 40x slower than native crypto. [1]:http://crypto.stanford.edu/sjcl/ http://crypto.stanford.edu/sjcl/