| Filename | Latest commit message | Latest commit date |
|---|---|---|
The forge and matrix containers belong to the services host, not to a hive. hive-priv's container-name validator still accepted hive-forge and hive-matrix for WriteNspawnFlags, WriteResourceLimits and RemoveServiceDropin; hive-c0re only ever sends h-<agent> names there. - hive-priv-sock/src/lib.rs: drop SIBLING_CONTAINERS, its only user was the validator, and its test. - hive-priv/src/main.rs: the validator accepts only h-<name> and returns the logical name, so write_resource_limits loses its non-h- fallback; test that all three requests refuse both names. - hive-priv/README.md, docs/trust-boundary/security.md: the allowlist no longer lists the forge and matrix. Fixes #5508 |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-priv-sock
Wire types for the hive-priv privileged-helper socket
(/run/hive/priv.sock) — the contract between hive-priv (the root helper,
server) and hive-c0re (client, via its priv_client).
Why it's its own crate
Split out of hive-sh4re so hive-priv — a root-privileged binary —
depends on just this narrow protocol crate instead of the much larger
daemon-shared crate. Two wins: fewer dependencies in a root process's supply
chain, and a small, self-contained interface makes the privilege boundary this
crate encodes easier to audit. Mirrors hive-host-sock's split for the host
admin socket.
Shape
Serde-derived request/response types only — no server or client logic. Both
sides import them so the shapes stay in sync. See docs/trust-boundary/boundary.md +
docs/trust-boundary/security.md for the privilege boundary these types sit on, and
hive-priv/README for the helper itself.