Dashboard and SSO logins issue an opaque, random session token. Only a SHA-256 of the
token is stored (in the sessions table, or in memory when no database is configured)
The cookie is HttpOnly, SameSite=Lax, and Secure on HTTPS; it expires after
session_ttl_minutes and is revoked on logout
State-changing requests authenticated by cookie are rejected when the Origin or
Sec-Fetch-Site headers indicate a cross-site request
Proxy listener targets and redirects are restricted to public addresses; loopback,
private, link-local (including cloud metadata) and other non-routable ranges are refused
Tunnel clients cannot ask the server to dial arbitrary hosts; all remotes are reverse
AI provider API keys are encrypted with AES-256-GCM. Set CHISSL_ENCRYPTION_KEY
(32 bytes, or any longer passphrase) in the server environment; without it a built-in
default key is used and a warning is logged at startup
SSO client secrets are write-only through the API (has_client_secret reports presence)