3 ms·
Yours is at best a terribly muddled description. Public keys are _public_ and we don't care if they're "Obtained by unauthorized parties" or "Disseminaated with
by tialaramex 7y ago
Yours is at best a terribly muddled description. Public keys are _public_ and we don't care if they're "Obtained by unauthorized parties" or "Disseminaated without your consent". That's what _public_ means.
The specific issue here is that the WebCrypto API is supposed to be protected against XSS. So if your code has a private key P and it turns out a bug in your site means bad guys can run whatever they want inside the VM where P is stored, they can't discover P. A bug in Firefox meant that it was actually possible to modify P and then do operations which have the effect of revealing it without undoing the virtual machine's protection for the actual value of P.
It's maybe hard to come up with concrete scenarios where this is a problem (which will be why it was so easy for Firefox to just remove it from the current version) but on the other hand it's also really hard to come up with concrete scenarios where WebCrypto was the Right Thing anyway so this is certainly not a point against WebCrypto sceptics like HN's Thomas Ptacek.