6 ms·
Seems like it would be better to go with S/MIME or OpenPGP for this. S/MIME would potentially be able to re-use some of the browser's own code for handling cer
by rdl 13y ago
Seems like it would be better to go with S/MIME or OpenPGP for this. S/MIME would potentially be able to re-use some of the browser's own code for handling certs.
Symmetric crypto (like this) is relatively easy to implement, but a usability nightmare.
A browser extension is still a lot better than a general webapp for security.
I wish someone issued "mail-from" auth personal certs for ~free to end users, integrated into apps for cert request/signing/etc. StartCom's StartSSL sort of does (for "level 1" personal certs), but their cert issuance UI is a huge pain. It really needs to work with the "I have no cert, I'm going to use an app for a specific purpose, I get a cert incidental to signing up for the service, I then can use the cert for other purposes", which none of the x509 crowd really support.
WoT on the certs would be cool too (which startcom is trying, but since it's a pain to use, there aren't enough people, so it doesn't work.)
- anemitz 13y agoStartSSL is also not a widely accepted CA which means Apple Mail (and others) will likely complain the certificate is not issued by a trusted party. It's an easy fix, but one that shouldn't have to be done. @rdl who is your go-to CA?
- jbraithwaite 13y agoNot rdl but I use Comodo[1] which is free for personal use. - [1] http://www.comodo.com/home/email-security/free-email-certificate.php http://www.comodo.com/home/email-security/free-email-certifi...
- rdl 13y agoStartSSL's roots are in a lot of things, they just don't have the class1 intermediate cert in places like Apple, and as a result it doesn't work by default. Which is pretty annoying, but easily fixed (provide the intermediate cert along with the end-user cert; since the root is already trusted, it does not bring up a warning.)
- alooPotato 13y agoActually we went down the gpg public/private key path first, and realized that was way worse in terms of usability. Even though with symmetric you have to enter the password, at least average users know what that means. Try to get an an average user to do a key exchange, backup their private key or even know what a key is as some other solutions require.....
- ams6110 13y agoThis is so true. At work, I never cease to be astounded at the number of people (supposedly computer literate, e.g. CS graduate students) who are just flummoxed by ssh keys. And ssh keys are relatively simple compared to GPG.
- dfc 13y agoUsers do not need to back up their secret keys for your system? Update: I wrote my question hastily; originally this read "private keys" instead of "secret keys."
- ams6110 13y agoIt's symmetric. There are no private keys.
- acabal 13y agoI looked into S/MIME when researching email crypto options. Someone please correct me if I'm wrong, but with S/MIME, you have to get a cert issued from a "trusted" provider--i.e. your employer, or Verisign, or Comodo, etc. If you don't, then a lot of apps either issue scary warnings or even just refuse to work with your self-signed cert. But if someone like Verisign or Comodo issues your cert, how can you be sure the cert they issued you hasn't been stored and shared with (for example) the NSA? S/MIME seems to have the same problem as SSL, which is that to be really usable you have to trust a big company to provide you with encryption, and that company can be hacked, coerced, etc. But whereas SSL traffic is typically transitory in nature which makes it tougher to meaningfully capture and store, your emails are not transitory and can be accessed much more easily.
- jacquesgt 13y agoThat’s not how public key cryptography works. You don’t go and buy an SSL certificate from a CA. You pay for them to /sign/ your public key, presumably after verifying your identity. You generate the public/private key pair, and then you keep the private key private. The CA could in theory sign Eve's private key along with metadata saying that private key belongs to you, but that just gives someone the ability to impersonate you. It doesn’t give Eve the ability to read emails that Bob sent to you with a key wrapped with your public key.
- jbraithwaite 13y agoAt least with Comodo's s/mime service, they provide you with the private key [1]. IIRC, Symantec/Verisign did the same thing. - [1] https://secure.comodo.com/products/frontpage?area=SecureEmailCertificate https://secure.comodo.com/products/frontpage?area=SecureEmai...
- nickf 13y agoNo, they don't. The keys are generated using in-browser controls (XEnroll/CertEnroll and HTML 'keygen' tag).
- 13y ago
- Osmium 13y ago> Symmetric crypto (like this) is relatively easy to implement, but a usability nightmare. Conversely, it's the only type of crypto the general public understands. "Enter your password." It bothers me that this is the case, but there you go. The biggest problem OpenPGP has right now is that you need to explain what public and private keys are to someone before they even have a hope of using it.
- grey-area 13y agoApple mail and Exchange Server already support S/MIME, so that might be a good option, though as you point out certificates are the issue.