3 ms·

Personally? https://masterpassword.app/ https://masterpassword.app/ It's like an anti-password manager. Doesn't depend on any specific device. Essentially it'

by branon 6y ago

Personally? https://masterpassword.app/ https://masterpassword.app/ It's like an anti-password manager. Doesn't depend on any specific device. Essentially it's a sane implementation of what others have already discussed below, in the other child comments -- using the name of the site to derive a secure, non-reusable password.

linsomniac 6y ago
I used to do this in the distant past, but gave it up because it didn't cope well with: - Sites that have different password requirements (some require special characters, some don't allow them, for example). - Changing my password on a site. I took a peek at masterpassword.app, but couldn't see that it solved these. Does it?
- branon 6y ago
  Barely. In order with your requirements, Master Password offers: - A choice between a few different password types (numerical, short, long, complex, phrase) for picky sites. It relies on you to remember which password type you used for which site. - A counter you can increment arbitrarily to generate new passwords for a given site. Again, relies on you to remember that you're on password #3 for site X, password #5 for site Y, ... I haven't reached a point where I've had to make heavy use of these features (yet) but if you use lots of picky sites, or change passwords very often, certain limitations will become apparent. If it's any consolation, passwords generated by Master Password tend to have a unique phonetic cadence -- that is to say, once you're familiar with the first or second syllable of your password for a given site, you'll know pretty much instantly if you're looking at the right one, despite not being able to reproduce the entire string from memory. This might make it easier to increment the counter several times in quick succession while being able to conclusively discard passwords that don't "sound right". YMMV of course. If this sounds like something you'd hate to do, Master Password may not be a viable solution. The Java-based desktop app somewhat solves these issues by (optionally) caching encrypted data about your passwords (site names, password types, and counters) on disk. However this could possibly end up defeating the point of "doesn't rely on any specific device", if the user grows to become reliant on the cached data.

by branon 6y ago

linsomniac 6y ago

I used to do this in the distant past, but gave it up because it didn't cope well with: - Sites that have different password requirements (some require special characters, some don't allow them, for example). - Changing my password on a site. I took a peek at masterpassword.app, but couldn't see that it solved these. Does it?

branon 6y ago
Barely. In order with your requirements, Master Password offers: - A choice between a few different password types (numerical, short, long, complex, phrase) for picky sites. It relies on you to remember which password type you used for which site. - A counter you can increment arbitrarily to generate new passwords for a given site. Again, relies on you to remember that you're on password #3 for site X, password #5 for site Y, ... I haven't reached a point where I've had to make heavy use of these features (yet) but if you use lots of picky sites, or change passwords very often, certain limitations will become apparent. If it's any consolation, passwords generated by Master Password tend to have a unique phonetic cadence -- that is to say, once you're familiar with the first or second syllable of your password for a given site, you'll know pretty much instantly if you're looking at the right one, despite not being able to reproduce the entire string from memory. This might make it easier to increment the counter several times in quick succession while being able to conclusively discard passwords that don't "sound right". YMMV of course. If this sounds like something you'd hate to do, Master Password may not be a viable solution. The Java-based desktop app somewhat solves these issues by (optionally) caching encrypted data about your passwords (site names, password types, and counters) on disk. However this could possibly end up defeating the point of "doesn't rely on any specific device", if the user grows to become reliant on the cached data.