One-click permissions with a passkey
Change what Rowsafe may do on a server from the dashboard, signed with a passkey the server checks.
Root decides what Rowsafe may do on each server (permissions). Pair a passkey once, and an owner or admin can change it with one click on the server's page. The server checks the signature itself, so neither Rowsafe nor a stolen dashboard login can allow more than root did.
Set it up
Once per person and server:
Start the pairing on the server
As root:
sudo rowsafe-allow --add-ownerIt prints a code like KQ7M-2XRD and a link, then waits up to 10 minutes.
Create the passkey in the dashboard
Open the link as an owner or admin. Check that the code, server name and address match your terminal. If someone sent you the link, click Deny.
Click Create passkey (phone, Touch ID, Windows Hello or a security key). The page shows its fingerprint, like 3F2A-91C3-0B7E-55D4.
Compare the codes on the server
The terminal shows the fingerprint it received. Answer y only if it matches your browser; otherwise n.
The public key is kept in /etc/rowsafe/owners (root's). The server's page shows who paired.
Change a permission
On the server's page, under What Rowsafe may do on this server, turn a permission on or off.
Confirm (Rowsafe says what else changes with it), then sign with your passkey. The server checks it and applies the change, or says why it refused. Where something isn't allowed, buttons like Allow restarts on this server lead here.
Each signed change is for one server, expires in minutes, and works once. It's in the audit log.
Turn one off without a passkey
Turning off needs no passkey, even before anyone pairs one: click and confirm. Taking power away from Rowsafe can't hurt the server, and nothing running stops. It's audited.
Two still need the passkey, since they change what can reach the server: the firewall and the pooler on public addresses.
To list or remove paired passkeys, on the server:
sudo /usr/local/lib/rowsafe/rowsafe-permissions owners
sudo /usr/local/lib/rowsafe/rowsafe-permissions remove-owner 3F2A-91C3-0B7E-55D4Ask your AI assistant
Every Do it yourself has Copy for your AI assistant, a prompt for Claude Code, Codex or Cursor on a machine that reaches the server:
On my server db-1 (203.0.113.24), run `sudo rowsafe-allow security-updates`. It lets Rowsafe install the system's security updates when someone clicks it in the Rowsafe dashboard; nothing changes until then. Show me the command and ask me before you run it, then show me its output.Rowsafe's MCP server has no tool that changes permissions.
Limits
- Pairing trusts the page you see. That's why you compare fingerprints at the terminal: they match only for your browser's passkey. Attestation isn't used.
- After pairing, Rowsafe can't allow more without your passkey. It only relays signed requests. It can turn permissions off (all but the firewall and public pooler), like an owner or admin.
- The passkey prompt doesn't show the change. A compromised dashboard could ask you to sign a different one; the server still checks signature, server and expiry, and logs who asked.
- The agent can delay or block a change, not forge one. Root's installer applies verified changes (its sandbox blocks network and new privileges).
- Synced passkeys work (iCloud Keychain, Google Password Manager); copies can't be told apart. Remove one you don't trust with
remove-owner. - Owners and admins only. Not members, API keys or AI apps.
- Not in Docker, where they're set where the containers are defined.