Passkeys and approvals
Signeto has two separate ways of proving it's you, and they do different jobs:
| What it's for | What it is | |
|---|---|---|
| Your account | Signing in on signeto.dev, in the app and from the terminal | A passkey. No passwords |
| Your phone | Approving what the agent asks to do | A key in the phone's security hardware, unlocked with Face ID, Touch ID, or a fingerprint or face match, for each approval |
Your account connects your gateway to your phone, but it can't approve anything. The rest of this page explains both.
Signing in: passkeys only
Signeto accounts have no password. You sign in with a passkey: a key pair that your device or password manager creates for signeto.dev, unlocked with your face, fingerprint or PIN. Every sign-in asks for that unlock.
Any passkey provider works:
| Kind | Examples | Good for |
|---|---|---|
| Built into your system | iCloud Keychain (Touch ID or Face ID), Windows Hello, Google Password Manager | Your own computer and phone |
| A password manager | 1Password, Bitwarden, Dashlane and others, through their browser extension | Every machine you use, including virtual machines and Linux |
| A hardware security key | A FIDO2 key that can store passkeys and has a PIN set | People who keep their keys on a physical device |
| Your phone, for another computer | In the browser's prompt, choose Use a phone or tablet and scan the QR code | A computer that doesn't have your passkey. Needs Bluetooth on both, so it often doesn't work in a virtual machine |
You can add more than one passkey: Sign in at the top of signeto.dev, then Account (api.signeto.dev/account/passkeys). Add a second one, such as a password manager as well as your laptop, so losing a device doesn't lock you out. Each passkey you add or remove sends a notice to your email.
Signing in from the terminal
signeto setup (and signeto relay register) never asks for a secret. It prints a link and a short code. Open the link in a browser, check that the page shows the same code, and approve it with your passkey. The terminal continues by itself. This works over SSH too: open the link on any computer where you have your passkey.
Signing in on a virtual machine
A fresh VM has none of your passkeys. Use one of these:
- a password manager's browser extension, signed in on the VM;
- Lost your passkey? on the sign-in page, which emails you a code that adds a passkey stored on the VM;
- or open the terminal's sign-in link on your own computer instead, as above.
Lost your passkey?
On the sign-in page, choose Lost your passkey? and enter your email. Signeto sends a 6-digit code (and a link). Entering it lets you create a new passkey on the device you're using, and nothing else. Signeto emails you a notice when a recovery code is used and when a passkey is added.
This means whoever controls your email can add a passkey to your Signeto account. Keep that mailbox secure. They still couldn't approve anything: see below.
Approving: your phone's hardware key
When you pair the Signeto app with your gateway, the app creates a key that never leaves the phone's security hardware:
- iPhone: the Secure Enclave. Apple's App Attest proves to your gateway that the key belongs to a genuine copy of the Signeto app on a real iPhone.
- Android: the Android Keystore. The phone's Key Attestation proves the same to your gateway.
Each approval needs Face ID or Touch ID on iPhone, or a strong (Class 3) fingerprint or face match on Android, and signs that exact request: the repository, the pull request, the commit. Your gateway checks the signature against the key it pinned when you paired, before it does anything. It doesn't take the relay's or your account's word for it.
So your account and your approvals are separate:
- Someone who gets into your account can't approve anything. They don't have your phone's key, and your gateway accepts no other.
- Someone with your phone but not its unlock can't approve anything either. Each approval needs Face ID, Touch ID, or a fingerprint or face match.
- Pairing a new phone needs your terminal. Pairing happens through a QR code your gateway shows, and the new device is then added to your policy, which (once a phone is paired) only an existing phone can approve.
Why no passwords
- Phishing doesn't work. A passkey only signs in to signeto.dev. A lookalike site gets nothing, where a password would work for whoever collected it.
- Nothing to leak. Signeto stores only your passkeys' public keys. A breach of our database gives an attacker no reusable secret, and passwords leaked from other sites are useless here.
- The unlock is built in. A passkey proves you have the device and requires its face, fingerprint or PIN check, so there's no separate code to type and no SMS to intercept.
- It matches what Signeto is for. Signeto exists so that a real person, on a real device, signs what an agent does. A password would be the weakest link in that.