And once your key is compromised once, everything you own is compromised.
This idea flies in the face of good security practices - don’t use the same password for everything. Especially without key rotation support. At least with oauth you can change your password and revoke sessions.
I don’t see this as an improvement.
People use the same password everywhere and when the sys admin forces an updated they increment the number at the end or beginning by 1.
I call it password++ .
This is why 2FA was invented. You have to break both things, but they can always be the same two things.
lol
i've had the same password since late 90s's
its 12 random letters, numbers, characters that I forced myself to remember...
Of course I only ever changed the 1st and last characters every few months.
Besides, you can revoke permissions in your signing device, you can use multiple keys (I have 8 npubs), but you only have to add them to your key keeper once, same way we all keep our passwords in an encrypted PW app.
By "one login", I don't mean "one key". I mean, literally, the workflow for logging in.
This is something that keeps people from using new software. As soon as they have to figure out how to login, they're like nah.
Nostr means you only need to learn this once and it isn't something propietary.
The workflow, sure, assuming all your devices support signing in with a key the same way (they don’t) but having to use multiple keys negates the convenience. At that point it just becomes a longer password.
I use Alby extension on desktop, Nostore on iOS, and several other apps just accept a nsec. A simple unified signin system may be the goal, but we’re miles from there imo.
I don't want to blow you off, tho. I've been thinking over what you said and I'm going to proposal a simple solution, later.
Need to take my daughter shopping, first. 😂
Is there a NIP for key backup and recovery to handle situations like this?
One clear protocol would be: create a master key locked in a vault or whatever, and have other lower security keys. But you also need a two-way signed attestation:
- master key: I control this other key.
- other key: I am controlled by this master key.
That signed attestation could be a VC that could be presented at any time to a compliant nostr client, for account recovery.
... but it would also need to be visible and supported by all consumers of your data that was assigned by your old key.
We have key delegation, but I don't know if that could be used for this.
Yeah it looks like NIP-26 "Delegated Event Signing" can be used for this.
The delegator would be the master key, and the delegatees would be the low-security keys.
It doesn't look like there's a revocation mechanism, and delegation has time bounds, so you'd need to generate new delegatee keys periodically. Which can be an airgapped operation.
