Users and SSH keys

Email codes for the console. Personal SSH keys for Git.

Sign in with an email code

A service administrator creates your account and enrolls your email. Enter that address at the console and use the fresh eight-digit code delivered to your mailbox. There are no passwords or public signup. An account without an enrolled email cannot sign in.

Codes expire after ten minutes, allow five guesses and can be used once. Requesting a replacement invalidates the earlier code. The response does not disclose whether an address is enrolled or disabled. Delivery and attempt limits apply.

Add a personal key

Open SSH keys in your console and submit a label and one complete public-key line. Ed25519 and RSA keys of at least 3072 bits are supported. Never submit a private key. Extra authorized_keys options are rejected.

You can create an Ed25519 key locally with OpenSSH:

ssh-keygen -t ed25519 -C "you@example.com"

Use the public file ending in .pub. Keep the private file on your own device. A key authenticates your identity; repository membership determines its access.

Revoke a key

Revoke a lost or retired key from SSH keys. Revocation keeps its fingerprint reserved permanently; the same fingerprint cannot be re-enrolled as a new key. The result distinguishes the policy change from termination of affected Git sessions. Add a genuinely new key when replacing one.

Manage accounts

Service administrators can create users, enroll or change email, enable/disable accounts and assign service administration. Users manage their own keys. Repository administration does not grant account administration or access to other people's keys.

Account edits invalidate existing browser sessions and pending codes. Disabling an account also changes its effective Git access. Preserve an existing identity when changing email rather than creating a replacement user with disconnected ownership.

Sessions and recovery

Sessions last at most twelve hours and survive ordinary daemon restarts. Sign-out revokes that session. Each request checks current account state and permissions. The essentials update also revokes the prior cookie after successful reauthentication; full-instance recovery invalidates restored sessions and login codes.

If mail is unavailable or enrollment is wrong, an operator must use the authenticated local CLI on the existing identity. There is no public recovery bypass. See troubleshooting.