Security
The durable authority authenticates publishers and voters, bounds every admission layer, and fences storage. Host-local reads trust the host.
Host-Local Reads
Section titled “Host-Local Reads”- A user agent’s runtime directory is private (
0700). - A system agent’s snapshot is world-readable (
0644) by design, and only writable by the service account. Every local user can read every knob. - Readers map the snapshot read-only and bounds-check every offset and length against the payload size before dereferencing.
- A file source accepts any valid snapshot in its file, so whoever can replace the file can publish to that host. Keep it writable only by the publisher.
Never put secrets in knobs.
Durable Authority
Section titled “Durable Authority”- Publishers authenticate with bearer tokens, over HTTPS when not bound to
loopback. Producer identity comes from the credential; each credential is
authorized for specific namespaces, and
publish: falsemakes it read-only. - Voters authenticate each other with mutual TLS plus a per-voter SHA-256 certificate pin. A semantic fingerprint in the peer hello rejects voters with a different quorum or limits.
- Admission is bounded at every layer: per-request bodies, aggregate bytes, request slots, per-producer concurrency, handshakes and connections, with deadlines on headers, bodies and writes.
- Configuration files holding tokens must be regular, single-link files, owned by root or the service account, without world access.
- Managed agents verify the authority’s certificate chain and hostname, and keep their token in a private file that readers never open.
Reporting a Vulnerability
Section titled “Reporting a Vulnerability”Please report security issues privately through GitHub security advisories rather than public issues.