http://www.w3.org/2011/11/webcryptography-charter.html http://www.w3.org/2011/11/webcryptography-charter.html Something like this is the ONLY way I can see cry

http://www.w3.org/2011/11/webcryptography-charter.html 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.