3 ms·
The solution should be to just stop using human generated passwords and instead have each site generate their own and for browsers and apps use password manager
by EGreg 8y ago
The solution should be to just stop using human generated passwords and instead have each site generate their own and for browsers and apps use password managers built into the OS and offer to fill them in based on the domain. This is increasingly happening. We need the large sites to move to this to eliminate phishing entirely. So https://f00l.com https://f00l.com isn’t same as https://fool.com https://fool.com
- mtone 8y agoI use Keepass and still manually paste and autosave my passwords. Have browsers extensions improved for this? When I last checked 5 and 10 years ago, it didn't seem to work.
- sokoloff 8y agoFor sites that I don't care that much about, I use and like Chrome's (relatively) new password manager [0]. I haven't looked into it in enough depth to be 100% convinced to trust it with my financially-linked passwords. (In reality, it's almost surely good enough, but I haven't reached that informed conclusion yet.) [0] - https://www.blog.google/products/chrome/chrome-password-manager/ https://www.blog.google/products/chrome/chrome-password-mana...
- L_Rahman 8y agoOh yes. 1Password X for Firefox and Chrome, 1Password on Safari have pretty much solved this problem. The vast majority of passwords I fill are CMD + [shortcut]. Generating and saving new ones works like that maybe 50% of the time. The failure rate however is driven less by the extension technology and more by the password form itself.
- Jaruzel 8y agoAll you've done there is move the attack target from the website to the users device. The obvious solution is to remove all users from the internet.
- EGreg 8y agoIs this a joke?
- Boulth 8y agoYes, that's exactly how U2F works (it's scoped to domain/origin). FIDO2 builds on top of that.