News for hackers. Stuff that matters.
Re:Stanford JavaScript Crypto Library by memexy on Monday June 15, 2020 @11:25PM (#23535671)
> One of the biggest default security improvements with Web Crypto is that *cryption keys are _not readable by JS_ once instantiated - they can only be used by the cryptographic functions (unless you explicitly make them exportable). This is a subtle but very important defense against certain drive-by attacks that could dump loaded keys from whatever non-native JS crypto library you might be using.

That's a really nice feature. This should be better advertised. I wasn't aware that Web Crypto was even a thing.

Re:Stanford JavaScript Crypto Library by codysc on Tuesday June 16, 2020 @12:11AM (#23535878)
Yes, that kinda HSMish model of non-extractable keys is a very nice touch. I really wish they would add Argon2 though. PBKDF2 is still a valid choice but there are a lot of HW optimized solvers out there for it.