I haven't seen this discussed here:
https://lesspass.com/#/https://blog.lesspass.com/I found out about it reading Jeff Atwood's Blog:
https://blog.codingh...-rules-are-bullshit/But as with many things, it came from the comments, not the article:
https://discourse.co...are-bullshit/5033/23(the reason I can't just stop reading the comments *sigh*)
A short blurb from the site (full info can be found at
https://blog.lesspas...742dd18a4#.d6uu4xx1q)
The trick is to compute passwords rather than generate and store random passwords.
LessPass generates unique passwords for websites, email accounts, or anything else based on a master password and information you know.
LessPass is different from other password managers that you can find on the Internet because:
It does not save your passwords in a database ;
It does not need to sync your devices;
It is open source (source code can be audited).
The system uses a pure function, i.e. a function that given the same parameters will always give the same result. In our case, given a login, a master password, a site and options it will return a unique password.
What about sites with strange requirements?
From the same link:
What about complex password rules?
Sometimes sites have specific password rules. For instance, some banks only accept passwords made of numbers. So you have to remember both a strong password and complex rules.
Well, we built a “connected” version to tackle that. It works by saving your password’s profile, i.e. everything –except the master password and the generated password– to be able to generate the password. Then, next time you need this password you just have to select the profile and type the master password.
Source is available on GitHub:
https://github.com/lesspass/lesspassAnd you can host your own instance in a docker container, if you don't want to use the public database.
Not quite sold enough to switch from lastpass, but I am thinking about it, and wanted to find out if anyone had seen/taken a look at this? Seems very simple, but very logical...