5 ms·
My company's internal mail goes through gmail so I decided after recent news to setup GPGmail and s/mime. I identified a couple of usability issues, which wher
by joshuak 13y ago
My company's internal mail goes through gmail so I decided after recent news to setup GPGmail and s/mime.
I identified a couple of usability issues, which where fixed. I'd say all in all its very good.
Regardless if you believe or care about the NSA issues, simply the idea of routing clear text email through mail exchanges, and advertisers should give you enough reason to follow the few steps it requires to generate a key, and start encrypting and/or signing email. Except for post cards we don't do this with our regular mail, so why are you ok with it with you email (and your email is far more machine readable).
GPGMail is not quite Grandmother ready, and unlike s/mime it doesn't really have an incremental value[1], but it is far more secure, and very easy to use once setup. Plus the other tools in the toolkit are useful for general encryption.
s/mime is another option, here are some pros and cons:
s/mime pros
integrated with many mail apps
usually plays nice with mailing lists (adding a footer doesn't invalidate a sig)
works on iOS devices (perhaps others?)
has an incremental value even before all your contacts are using it[1]
s/mime cons
based on a certificate authority model
cost money depending on the cert you get
requires a 3rd 'trusted' party
does not seem to be secure in some respects:
(web cert generation, no rules regarding sigh/encrypt/sign[2],
does not make use of a certificate request so anyone who has
even momentary access to your email can generate a cert to
masquerade as you)
your identity is associate with your email address not you
(you will need certs for each email address)
--
GPGmail/tools pros
Based on web of trust instead of CA (web of trust is not required)
You can revoke your key if it is compromised
Based on you not your email, so you can use the same sig with any email address
You can even associate your picture with your key
Optional Anonymity
Strong cryptography
Use the same keys for non email encryption
Free
GPGmail/tools cons
Less widely integrated.
Does not work on devices yet.
May break email lists (adding footers may change the sig, I haven't tested though)
Can't help much until your have other people to use it with.
[1] With s/mime you can sign email documents even if your friends don't have s/mime that can still see your signature is validate.
[2] See the answer by Adam Liss (not the accepted answer) for the security issues http://stackoverflow.com/questions/13512026/how-to-check-if-encrypted-s-mime-message-is-also-signed-without-decrypting-it http://stackoverflow.com/questions/13512026/how-to-check-if-...
[Edit: formatting]
- munin 13y agoyou can revoke your S/MIME key from a CA (you just need to remember the revocation password you gave them) S/MIME is also built in to (almost) every thick MUA. it works on iOS out of the box, it works in outlook, thunderbird, mail.app and mutt out of the box. once you generate a S/MIME cert through a big provider, none of the other big providers will give you an e-mail cert for the email issued by the other big provider (probably, still trusting them to do the right thing).
- joshuak 13y agoNo, you cannot revoke your s/mime cert. Your CA can. That is a big difference.
- claudius 13y agoJust two nitpicks: You can sign email with GPG even if others aren’t using it (of course it will be of little value to them until they, possibly at a later date, verified your key), and it is supported on Android by K-9, I believe.
- joshuak 13y agoYes you can, but my point was that this is of no utility with GPG. Whereas with s/mime anyone can confirm that your email was signed (with many email clients), so there is value to using s/mime prior to all your contacts also using it.
- claudius 13y ago> anyone can confirm that your email was signed (with many email clients), so there is value to using s/mime prior to all your contacts also using it. Provided that they trust the people handing out these certificates – with PGP, they need a chain of trust to your key to verify that it is you, with S/MIME, they have to trust random third parties. Or do I miss something and you mean something else that is possible with S/MIME but not PGP?
- 13y ago