Expand description
Launch-token authentication for the supervised uar-sidecar process.
The host that launches the sidecar writes a per-launch 256-bit token as the
first line of the sidecar’s stdin. SidecarGuard then admits a request
only when it carries that token, names the sidecar’s own loopback authority,
and carries no Origin header. A loopback port is not an authentication
boundary: any local process, and a web page through DNS rebinding or a
cross-origin request, can reach it. See the OpenSpec change
sidecar-launch-security.
Structs§
- Host
Authenticated - Marker installed only after the outer launch-token guard admits a request. Inner authentication may trust host assertions only when this marker exists.
- Invalid
Launch Token - The first stdin line was missing or was not a well-formed launch token.
- Sidecar
Guard - Per-request admission for the sidecar port.
- Sidecar
Launch Token - The token the host handed the sidecar over stdin.
Functions§
- enforce
- Outermost middleware of a token-authenticated sidecar.