Re:Cryptography in the Browser
by jxson on Tuesday October 29, 2013 @07:34PM
(#6638324)
Progressive enhancement is a real thing and as the browsers start to implement native support for the rest of Web Cryptography API the situation will only improve. We have to start somewhere.
[ Parent
| on HN ]
Assuming that browsers have implemented Web Crypto, how do you know you're using it and not an evil polyfill?
Re:Cryptography in the Browser
by blazingice on Tuesday October 29, 2013 @10:00PM
(#6638962)
Some JS engines already disallow security-violating operations from happening (such as inserting evil hooks into document.location). These same protections could apply to any Crypto object.