It would likely be safer than hamfisted attempts at JS cryptography which can be compromised down the wire.
It would likely be safer than hamfisted attempts at JS cryptography which can be compromised down the wire.
Unfortunately so far things are moving in the opposite direction. After Chrome dropped Java support it appears there's no cross-browser way to do reasonably reliable crypto right now.
2. client certificate distribution is still a mess. At a minimum, there should be a standard way for servers to generate certificates and install them in the browser (with user visibility but without requiring user interaction).
2) You mean something like keygen[1]? (yes, I know it was removed from the standard.)
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ke... (
2) Exactly. I don't follow the standard process these days, but it's sad that we're not really making any progress in such a critical area. We now have pretty progress bars, but we're still as vulnerable as 20 years ago.