3 ms·
The WebCrypto API is meant to solve this but many aspects of it are not quite ready for production yet. I'd personally love to see JS crypto libraries like Cry
by lewisl9029 12y ago
The WebCrypto API is meant to solve this but many aspects of it are not quite ready for production yet.
I'd personally love to see JS crypto libraries like CryptoJS, SJCL and Forge start implementing polyfills for WebCrypto. Even just using the getRandomValues method (which seems to be fairly stable across all modern browsers) for their PRNG implementations would result in a much more theoretically sound crypto library.
http://www.w3.org/TR/WebCryptoAPI/ http://www.w3.org/TR/WebCryptoAPI/
https://github.com/digitalbazaar/forge https://github.com/digitalbazaar/forge
https://github.com/bitwiseshiftleft/sjcl https://github.com/bitwiseshiftleft/sjcl
https://code.google.com/p/crypto-js/ https://code.google.com/p/crypto-js/
- tracker1 12y agoI'd like to see more async implementations of crypto for JS, breaking work up with setTimeout/setImmediate so that they don't kill the browser... Lately, I'm more inclinded to first reach for the browserify polyfills, and use the node crypto api.