Accounts
Nobody has to sign in. Each browser has keys of its own, kept between visits, and what it writes is signed with them. An account adds one name for a person on every device and every app, still with no company holding it.
Without an account
A PeerPigeon node makes a key pair the first time it runs and keeps it in the browser. node.getKeyPair() returns it (secret keys included), and node.storage.signer() is the public key that signs its records. Clearing the browser makes a new identity, unless the keys are given back as crypto.keyPair.
With PigeonIdP
PigeonIdP accounts are signed records kept by relays: a name, the public keys, and the private keys sealed with the account's password. Signing in on a new device fetches the record and opens it with the password; the relay never sees the password or an open key.
- A relay keeps the first record for a name, and afterwards only a newer one signed by the same key, so a name can't be taken over by registering it again.
- Records are post-quantum (version 2): ML-DSA-65 and ML-KEM-768 keys next to P-256, the record signed with both, and the keys sealed with Argon2id.
- The same accounts work in every app on the network: a PigeonChess account signs in to PigeonFeed.
Signing as an account
After signing in, an app tells its storage to sign as the account:
node.storage.signAs({ pub: account.pub, priv: account.priv })From then on, what the page writes belongs to the account, on every device that signs in to it.
Without crypto.subtle
Browsers leave out crypto.subtle on plain-http pages (a build served at a LAN address, say). UnSea then uses its own stand-in for hashing, key derivation and AES-GCM, with the same results, so keys, signatures and accounts work there too.