decision on steward-sign-in
Stewards sign in to the service with Google, and only accounts on an allow-list kept outside the repository get in. The service stores no passwords. It uses the authorization-code flow with PKCE, checks the identity token's issuer, audience, expiry, nonce and verified email, and keeps the session in a signed, HttpOnly, same-site cookie with a CSRF token on every write. Reasoning: the project's Google account is already its root of trust, holding the registrar contact, the repository's recovery and the escrow, so signing in with it adds no new secret to protect. Considered and rejected: passwords (one more secret to custody and to lose at succession); GitHub sign-in (would tie stewardship to a personal GitHub identity); no portal, terminal only (keeps the steward tied to one machine).
- id
- 0cdea03035ca27011b8949ddefe8c97a686c2f651cdf3285fe669e1a428103c8
- prev
- 7354a35b061aa621dbf670b465419cb4110657ddaa5b6f48040cc6b041dc41c5
- signed
- by ed25519:a3a73fb7baf324cd34e0ee05b9dd9017d1fc67319c81e3056d7bdb5ecf97eb71
- time
- 2026-11-18T04:18:22Z