docs: Control UI identity + gateway pairing hardening + release verification

This commit is contained in:
Vincent Koc
2026-04-22 23:52:37 -07:00
parent ea3970f138
commit c8aec6b951
6 changed files with 83 additions and 0 deletions

View File

@@ -941,6 +941,15 @@ Local device pairing:
trusted shared-secret helper flows.
- Tailnet and LAN connects, including same-host tailnet binds, are treated as
remote for pairing and still need approval.
- **Forwarded-header evidence disqualifies loopback locality.** If a request
arrives on loopback but carries `X-Forwarded-For` / `X-Forwarded-Host` /
`X-Forwarded-Proto` headers pointing at a non-local origin, the request is
treated as remote for pairing, trusted-proxy auth, and Control UI device
identity gating — it no longer qualifies for loopback auto-approval.
- **Metadata-upgrade auto-approval** applies only to non-sensitive reconnect
deltas on already paired devices (display name, client platform hints).
Scope upgrades (read to write/admin) and public key changes still require
explicit re-approval and are never silently upgraded.
Auth modes: