LessPass even stole the "one password to rule them all" phrase and the idea of "profiles"
There are still many active ports of ports of PasswordMaker:
https://www.google.com/search?q=github+passwordmaker&oq=gith...
Heres the original web version:
That phrase is a reference to Lord of the Rings, and an obvious one at that. Doubt passwordmaker was the first or last time someone comes up with that line.
That may be true. But this isn’t a great example of it. This is pretty much the most naive (not in a bad way) evolution of password management possible:
Q: I need passwords for all my accounts. What should I do?
A: Use the same master password everywhere.
Q: But if one service has a leak all my accounts are compromised
A: Then just combine the password with the url. Like password|url.
Q: Well that helps against automated approaches, but a human could pretty quickly deduce all my passwords.
A: Hash it.
Q: Cool. Now what about when I need to rotate a password for an account.
A: Add a version number and hash that too.
Q: Cool. Now what about when I have different accounts with the same url.
A: Just hash the account name too.
Q: Cool. What about some websites that have specific password requirements?
A: Uh. Map the hash to a language with the symbols you need and try to remember what that language was when you need the password again.
Not answered, but interesting to consider:
How can I avoid needing to remember the language? (Online service mapping domains to password requirements? But then what about then they change over time?)
How do I remember what version number I’m on? (Online public mapping from hash(username|url|userID) => number? But who has write access? Everybody... blockchain?!?? This could also solve above question. )
Funnily different master passwords generate a different output space ( good if you want special characters), which is a tiny bit worrying.