3 ms·
1. Why don't passworded websites provide their own password generators? There's "secure" entropy generation available to JavaScript, e.g. `Crypto.getRandomValu
by Zamicol 5y ago
1. Why don't passworded websites provide their own password generators? There's "secure" entropy generation available to JavaScript, e.g. `Crypto.getRandomValues(Uint8Array)`.
2. Shouldn't the only variable for password generation be entropy/information?
Here's a 256 bit password:
1NH8O3C3GH33FNQHM3B7VFKIQ95EMD-QLPOFPPYJ54NCFXMOB3
How could you know?
An easy way is to take the character set and convert the input string to binary. Once you reach a specified information level (say 256 bits), then the password could be considered sufficient.
https://convert.zamicol.com/?in=1NH8O3C3GH33FNQHM3B7VFKIQ95EMD-QLPOFPPYJ54NCFXMOB3&inAlpha=0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ-&outAlpha=0123456789ABCDEF https://convert.zamicol.com/?in=1NH8O3C3GH33FNQHM3B7VFKIQ95E...
3. Combined, I'd imagine a decent user experience.
4. I can't wait for public key authentication to kill passwords.
- wruza 5y agoI believe this doesn’t account for dictionary-based attacks. “qwerty secret 123456” may even have decent entropy in ascii space, but can be bruteforced in minutes because these words go first in the weighted list. (Not a security expert)