Security › Sandbox More Every side that builds or calls a sandbox shares three boundaries. The
Sandbox Contract
defines the shared inputs. Bridges
explain how callers supply identity and grants. The
Filtering Proxy
covers the HTTP boundary that approved requests cross.
Docs Runtime Maintenance : Read Sandboxed SSH Sessions for session state and Worker Controller Maintenance for worker supervisionBridges : What every bridge out of an agent's sandbox speaks, through link-sandbox-bridgeFiltering Proxy : The package link-sandbox-proxy is the sandbox's one way out, a filtering proxy that Local Link runs outside the sandbox, with a table of routes that names none of themSandboxed SSH Sessions : On a box, a person gets a Linux user of their own, whose every SSH session is in their sandbox: A box's usersWorker Controller Maintenance : The worker installer maintains an ordinary Linux box's privileged launcher and controller identitySandbox Contract : link-sandbox-contract: the sandbox's policy, independent of its implementation