vole
Clone
Read only, no credentials:
https://rodent.software/vole.git
Write over SSH with a registered key:
git clone ssh://git@rodent.software:2222/vole.git
A free and open-source forge that lives in your Git repo.
Let people rename and remove their own passkeys
7d7718fac3edfc9b8e27d1e55721a6f9ca9106af · Keenan Nemetz · 7h ago · parent 5f6163bb
Let people rename and remove their own passkeys The Account page listed and added passkeys and could do nothing else: a lost or shared device, or a label typo, needed an instance admin and the CLI. Both are the person's own credential, so both belong on the page. - Rename: `identity.RenameCredential` writes the label in one transaction and audits `identity.credential-rename` with the passkey and its new label. A label is display text, so the credential id and key are untouched and the cap is the one the ceremony already uses (`MaxCredentialLabel`). An empty label is allowed and the page calls it a passkey. - Remove: `identity.RemoveCredential` now deletes the sessions of that passkey in the same transaction. The foreign key cascades already, and saying it out loud is what makes it the intent rather than a schema accident: the session the person is reading the page from ends with the passkey it signed in with. - The last passkey is refused, with an explanation, while the account has no SSH key either. With one it is a way in for Git, so an account that has one loses only its browser sign-in; with neither, the only way back is an admin invite, and losing that should never be a click that silently succeeded. Two passkeys are enough to rotate: the last one is protected, not every one. - The page gets a rename form and a remove form per passkey, each with the CSRF token and a confirmation on the removal, and a line saying what removing one does. The handlers are scoped by the session account, so the form cannot name somebody else's credential, and an unknown one is a 404 rather than a silent no-op. Docs: `docs/accounts-and-access.md` covers renaming, the last-passkey rule, and the audit actions for both. Tests: the label changes and the credential does not, an empty label clears it, an over-long one is refused where it is accepted, and another account's passkey is not renameable; a removed passkey takes its sessions with it (identity); and end to end over the account page — rename one of two, remove one of several, a post without the token is refused, and the last passkey is refused until an SSH key is added. Closes 01M6SASJYFVH6Z3P6BXTEMA83
server/routes.go +2
| @@ -99,6 +99,8 @@ func (s *Server) authRoutes(mux *http.ServeMux) { | |||
| 99 | 99 | mux.HandleFunc("GET /-/account", w.AccountPage) | |
| 100 | 100 | mux.HandleFunc("POST /-/account/keys", w.AddAccountKey) | |
| 101 | 101 | mux.HandleFunc("POST /-/account/keys/remove", w.RemoveAccountKey) | |
| 102 | mux.HandleFunc("POST /-/account/passkeys/rename", w.RenameAccountPasskey) | ||
| 103 | mux.HandleFunc("POST /-/account/passkeys/remove", w.RemoveAccountPasskey) | ||
| 102 | 104 | mux.HandleFunc("POST /-/account/passkeys/begin", w.AddPasskeyBegin) | |
| 103 | 105 | mux.HandleFunc("POST /-/account/passkeys/finish", w.AddPasskeyFinish) | |
| 104 | 106 | } | |