> I think you should port to a browser extension Chrome extensions are HTML5/JS... which wouldn't stand to your own argument. > Unfortunately, the 10 years si

> I think you should port to a browser extension Chrome extensions are HTML5/JS... which wouldn't stand to your own argument. > Unfortunately, the 10 years since 2005 have made browsers less hospitable to cryptography. You're saying IE6 and Firefox 1.0 were better for cryptography than our environment today? We've got effective standards like CSP and CSP2 for restricting code execution client side, SRI for validating resources hosted beyond trust boundaries, HPKP and HSTS for ensuring trust on TLS connections, and we have cooperation between major browser vendors to implement patterns like HSTS preloading and even certificate preloading for certain sites such as Twitter, environment sandboxing introduced as early as 2007, and your assertion is that the browser environment now is less hospitable to cryptography than in 2005? You were right a few comments ago; there's no point debating this any further. I have to do some shoveling anyway.