| Filename | Latest commit message | Latest commit date |
|---|---|---|
e56fc97be8
The network-isolation doc comments carried prose docs/network.md already owns, and three of them named `harness-base.nix` — a file that does not exist. The `hyperhive-isolated-dns` oneshot lives in nix/agent-modules/network.nix, which the doc gets right. That is #3749's argument reproducing itself: the same fact written in two places goes stale in the copy nobody reads. Linking removes the class, not just the instance — a link cannot name a nonexistent file without the doc noticing first. Trap and measurement comments stay put, per the issue's scope: the load-bearing HOST_ADDRESS default-route note, the unquoted $EXTRA_NSPAWN_FLAGS expansion, and the "isolation is the only mode" invariants are facts about this code, not about the subsystem. |
||
| .. | ||
| 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/boundary.md +
docs/security.md for the privilege boundary these types sit on, and
hive-priv/README for the helper itself.