Pairing
Pairing is the only hand-over of keys. Tailscale proves a device is on your network, but anyone you share the network with could otherwise drive your server. A pairing code says “this device is allowed”.
Why pair
Each paired device gets its own token; revoking one does not affect the others. The code is the one time a secret changes hands — and it does so inside the encrypted Tailscale session.
How
- The installer prints a code; later codes come from
trailSailServer pair --newon the server, or from Pair another device… in the panel of any paired TrailSail. - In TrailSail: Settings → Server → Pair with a server → the server's tailnet name and the code.
- The code is six words, single use, valid ten minutes. Five wrong codes lock pairing for ten minutes.
What you get
- The engine addresses and keys.
- Your control token.
- Ready-made connection profiles for Splash and the router. SearXNG's address goes into Web search.
Everything secret goes to the macOS Keychain; nothing is written to disk or logs.
Keys over time
- Rotate API keys from the panel: new keys are made on the server, the engines restart, and every paired device fetches the new keys on its next poll. Control tokens are separate and are not rotated by this.
- Revoke a device from the paired list; it must pair again with a new code.
- Forget a server on a device to drop its token there; the connection profiles stay.
Phones and tablets
Any device running Tailscale pairs the same way, including over 5G.
Found a problem, or is something here unclear? Report it.