The idea of a security tool using the same name as one of the most serious security vulnerabilities of the last decade is very funny, lol.

This is extremely impractical for daily password use. Not being able to ever change your master or the passwords to your sites is a deal-breaker for the security minded who wouldn’t even want the risk of an encrypted password wallet.

This seems like someone learned about key derivation functions and applied it to passwords. So with this system, it’s stateless and no passwords are stored (encrypted or not). You need 4 things to generate passwords:

• Your full name
• Spectre secret
• Site Domain
• Master password

This seems counter intuitive to the stateless nature, since at least one (the spectre secret) will need to be stored somewhere. For UX the full name probably would also be stored, and the site domain can be gotten via some API on password use. This leaves the master password as the only portion not stored, and on “unlocking” the database it would probably be stored on the users device for a period of time.

This also ignores some of the requirements of websites needing passwords (some support all characters, some only a-z0-9_, etc etc). If supported, this metadata would also need to be stored somewhere. The cons of not being able to change passwords is also a huge issue, as passwords should be changed often, or replaced with keys (which you also replace often!).

For attackers, this seems not much different than a database file. In most cases, they’ll already know two of the 4 (site domain and full name, especially in corporate environments). This leaves only the spectre secret and the master password doing the heavy lifting of security. This sounds a lot like a traditional password manager, where you have a master password, a database file, and an optional key file.

So the process to attack a traditional database system is to acquire the needed information (database file, master password/key file) and lookup the password (site domain/description). The process to attack spectre is to acquire the needed information (full name, secret, master password) and lookup the password (site domain/description). These have the same challenges of acquiring/brute forcing the master password and key file, and are essentially the same in the eyes of an attacker.

Overall I think passkey’s will replace passwords, or something along that line. Keys have been used for a long time in security sensitive areas, can be swapped out easily and provide much more protection than a password when large enough.

So… you need a master password, you can not switch your master password, any password you generate can not be changed in case of leaks or ugly police to change every X days. Plus, having access to your master password give you access to every single password you ever created or will create.

I stay with single master password with random password.

if my securely generated password to example.com gets leaked in a data breach, my only options are to ignore the leak or regenerate all my passwords with a new master password?

i don’t think this works for me

This is often called a “stateless” or “generative” password manager, and while they do have some benefits they tend to be rather niche.

The main issue is losing the ability to easily change the master passwords as well as making it more difficult to deal with password requirements.

Also, for most users the sort of access needed to steal an encrypted password vault isn’t much different from what is needed to grab a master password as its being used, so the benefit is very limited.

There are some things I’m missing.

What if I need or want a certain passwod length? Because a site only allows X or I want to have Y amount of signs.

What about the control over special characters in the password or not. Sometimes I need to generate passwords without any special character.

Where is the 2FA aspect? Sure there is no datavse with my passwords. But at least my DB is secured with username + password + 2FA Code

I still need to trust a website or app where I put my credentials in. Or is it 100% offline? Like I am with KeePass and/or selfhosted Bitwarden at home.

How do I change passwords without the need of keeping track of website name changes?

And just as a note, things like Bitwarden or KeePass are much more than only a password generator.

Extra note: we are heading towards a passwordless future with passkey etc. anyway.

Calling this “manager” seems a bit of a stretch. What exactly does it manage? It only seems to derive passwords. Unless I have a database I can search in (and get convenience shit like the information how old or weak existing passwords are or maybe even which sites have been compromised in the meantime), I would not call it a manager.

I will stick with keepass

So basically a fancy hashing algorithm to get the same password for the same information you give it. Neat idea but I am not convinced yet.

If your Spectre secret gets somehow leaked (and your full name could easily be found), that’s immediately all your current and future passwords leaked. Now, this would in theory also be a problem with regular password managers that live in the cloud. Though smart ones hopefully add 2FA or similar before they let their users log in. For offline password managers the hacker would need your secret + database to get your password. That’s a lot harder. Spectre takes one of those items away, because the ‘database’ is their algorithm which literally runs on their webpage. All they need is a single password.

What if a site you use leaks your password and you have to change your password for that site only? Spectre won’t help you with that, as it will still give you the (burned) password. So you manually have to remember which sites use Spectre for passwords and which ones don’t.

Have any services that have been provided to you with a set password you can’t change (eg: some service your job uses), Spectre won’t help you with this as it won’t hold any custom passwords. Have any weird services that requires a specific length and/or forbidden characters Spectre does? Good luck, Spectre can’t help you here either. It’s not a password manager.

Seems like you’ve got it right, but I don’t think a lot of security minded folks who moved to a system like this would scoff at changing their passwords again.

I would absolutely migrate to this if there were a good android app for it. The one that exists doesn’t seem to have support for android’s password autofill system though

Have been using a manual method of consistently generating passwords for a while now so given good app/browser extensions it’s a direct upgrade

@imaginary doesn’t seem to be that much of a novel concept. I was interested into such a password manager that generates your paswords each time you access it instead of storing them. Indeed, for some (probably security related) reason you have to change your passwords to every service you use

I actually see myself being able to use this password manager; although it really does require that you approach passwords with a much different paradigm.

1. Spectre requires 3 input values. A “Full Name”, a “Master Password” and, a site name or domain name.
2. In order to manipulate the passwords provided you must manipulate these three values.
3. We can assume that “Full Name” is only changed or rotated when you are changing identities
4. We can assume that “Site Name” is only different when you are logging into a different website
5. We can assume that your “Master Password” or “Secret” is any old arbitrary string you choose.

Depending on the behavior of this generator we can always vary our input for #5 and, maybe vary the input for #4. I don’t know if it allows us to manipulate #3 after initial input though.

If 3 and 5 are variable with each use and 4 is auto-detected through software means, and stapled to the domain name value, then we already have two factors of information and we can use two ‘passphrases’ to derive one. You could insert a nonce into your First Name or Master Password. Maybe you only change the nonce word in your Name when making accounts for different purposes and change the nonce word in your Secret when a site needs a new password.

Full Name: First <Nonce> Last (change the nonce to change the account selected) Master Secret: Password <Nonce> (Change the nonce only when you need to kill the old password.

You remember: The Name, Secret, the Name Nonce and, the Secret Nonce. (This compresses down to three things if the nonce is same for both because the account has never been breached)

If only 5 is variable after initial setup and 3 is written only once and 4 is automatically determined; we can still vary the input of that to increment the passwords. You just have to add a nonce value or counter to your master password: MasterSecretHere <Nonce>

You remember: Master Secret and the Nonce. Maybe you have to remember if you’ve changed the Nonce for this website if it’s been breached.

If all three values are input to generate the password by you; then you have complete control over the generated password. You can insert your nonce into any, some or all of the values to change the desired password output.

Your remember: All three base inputs; Full Name, Site Name, and Master Secret. You may use as many or as few nonces as needed and you can make them memorable.

(Maybe Bad) Nonce Examples: (Please; be more creative than these nonces; these are only here to explain things.) [Please note that all names, sites and passwords/secrets presented are fictional and used only for example purposes. Do Not Use any of these examples as your own password generation inputs]

• First (Assumes Name and Secret can be variable; but not site name)

  • Full Name: Harry Muggle Dresden In this case; we use ‘Muggle’ as a memorable nonce to select his “Muggle” or “ordinary accounts” for handling his real life stuff like bank passwords.
  • Site Name: somewherenationalbank.com We assume this is set by his helpful browser plugin and he’s never had another account here; so we choose not to add any nonce here (if we even could).
  • Master Secret: Abracadbra-Alpha Here we follow a simple nonce list; since we haven’t needed to change the password yet; But if for some reason the bank gets a wild hair up it’s rear end and requires a new password; we would just cycle through the list of nonces as follows; Alpha, Beta, Delta, Gamma, Iota, Kappa, Omega

• Second (Assumes only the Secret is variable)

  • Name: Harry Milford Dresden
  • Site Name: spicymeatballsubsanywhere.com
  • Master Secret: Alakazam!Alpha He knows those nasty heckers at the FBI has been trying to snoop on his secret sub orders…so he’s using a different Secret base; Alakazam! to throw them off and prevent hacking. He would still just cycle through the list of nonces as follows; Alpha, Beta, Delta, Gamma, Iota, Kappa, Omega …if the password needs changing.

• Third (Assumes all three can be input at each password creation/retrieval)

  • Name: Harry <Purpose> Dresden You see; he’s a Wizard; so for times he’s being a Wizard for a client he uses Wizard, when he’s enforcing magic law he uses Warden and when he’s doing mafia work he’s using Winter to replace the <Purpose> token.
  • Site Name: <Username>@<domainname.tld> This should be obvious but this encodes his username and site name here.
  • Master Secret: <Passphrase>:<nonce> Pretty easy; he has a different passphrase for each purpse; all secret of course; and if a site gets hacked he changes the passphrase; if a site just needs a new password he changes his nonce by just cycling through the list of nonces as follows; Alpha, Beta, Delta, Gamma, Iota, Kappa, Omega