3 ms·
This is a great, straightforward idea. But the main problem with these kinds of approaches is that the system breaks down if you ever need to change any of your
by johnsoft 13y ago
This is a great, straightforward idea. But the main problem with these kinds of approaches is that the system breaks down if you ever need to change any of your passwords. There's also the problem of sites with password restrictions like alphanum-only, or maximum of 8 chars, which are unfortunately things a practical password scheme would need to deal with. I think KeePass (or one of the alternatives) paired with a browser extension is still the best solution out there right now.
- gtrubetskoy 13y agoThat's easy to work around - use google2, google3, etc as the keyword. A more "industrial" implementation might actually store secure hashes of past/void passwords and increment a nonce until we get a "new" one. The underlying crypto is still sound.