Re:Time for a return of the Cypherpunks, Crypto-Anarchists &...
by dekz on Monday April 23, 2012 @04:38PM
(#3880851)
http://www.w3.org/2011/11/webcryptography-charter.html
Something like this is the ONLY way I can see crypto in the browser gain any credibility and traction. Crypto in the JS is not only potentially the easiest attack vector, it's also abhorrently slow. With native browser constructs we get access to safe(r) implementations which cannot be DOM manipulated, MITMed or simply replaced at load time. We get access to speed boosts by running natively and on hardware supporting AESNI it can zoom.
There's the remaining problem of key management, though for many people, browser-based password managers are a reasonable mechanism.
PGP/GPG and TLS still provide key management issues (with several notable registrar incidents in the past year). And even if you're, say, parking a public key on a site to autoencrypt material sent there (assuming it's not encrypted prior to upload), there's the question of how you're going to interact with encrypted data on that site. I see three basic options: server-side encrypt/decrypt, browser-based, or client-side non-browser utilities. In the latter case, you now have a wide range of environments (Windows variants, Mac, Linux, etc.) to support.
Not saying it can't happen, but good crypto is hard.
Even the pros (PGP) ended up using a server-based solution which had both public and private keys on it as their solution to the key-management problem.