Issue 339: the node-engine places and mounts nothing at the machine's own trees, and uses a found directory as found #63

Merged
mesh-admin merged 2 commits from fix/339-the-engine-places-nothing-in-the-machines-own-trees into main 2026-10-08 22:36:46 +00:00
Contributor

Critical security fix (hq issue 339). Do not merge without review. Independent of mesh-controller's PR for the same issue; either may merge first.

The engine (root) chowned and chmodded whatever directory a declaration named — through a link too — and mounted whatever an access or volume named. A places setting at /etc with a caller's uid therefore handed it /etc.

New internal/apply/placement_guard.go, judged before anything is applied; each refusal is a failed resource with its reason in the node's report (PlacementRefusedError, "… is not placed: … (novox/hq issue 339); nothing was touched"):

  1. a directory, access or mount source that is, or holds, one of the machine's roots (/, /etc, /usr, /var, /var/lib, /home, /run, /boot, /root, /proc, /sys, /dev, /var/lib/mesh, …);
  2. a directory or access in /proc, /sys, /dev, /boot, /root, or the engine's own trees (but its own module); a mount from /boot, /root or the engine's trees (kernel files, devices and the clock stay mountable: systemPath plumbing);
  3. a non-root directory below /etc, /usr, /run; an access anywhere there;
  4. below a home, a directory not owned by that home's account;
  5. a container mounting any refused directory or access (it is not run).
    Every path is judged as declared and with links resolved.

applyDirectory: Lstat; a directory whose last component is a link is refused. A directory that was there before this apply and that the mesh has no record of applying at this path is used as found (owner and mode left, said in the outcome, recorded as_found, never removed) — ADR 0182 beyond the home. Every directory on a running machine already has a record at its path, so nothing applied today changes.

Tests that fail on main (run there first, guard-only test removed since it calls new functions): TestNoDirectoryIsPlacedAtTheMachinesOwn, TestNoAccessIsAtTheMachinesOwn, TestNoContainerMountsTheMachinesOwn (on main the container was run), TestALinkIsNotFollowedToTheMachinesOwn (on main the link's target was chmodded), TestAFoundDirectoryIsUsedAsFound (on main chmodded to 755). Plus TestBelowAHomeOnlyThatAccountsDirectoryIsPlaced and TestAModulesOwnPlacesAreStillPlaced.

Live check: the guard was run (throwaway test, not committed) over the declarations mesh-controller.plan composes today for all four nodes — 356 directories, 96 containers, all accesses: nothing refused.

Not taken from #61: the archive/into refusal below a root: never home (needs #61's Root field) and the home-itself refusal (the anchor's backup repository is placed directly under the homes' root; as-found covers a home).

merge-check.sh passes locally.

hq: issue 339 (PR to follow).

**Critical security fix (hq issue 339).** Do not merge without review. Independent of mesh-controller's PR for the same issue; either may merge first. The engine (root) chowned and chmodded whatever directory a declaration named — through a link too — and mounted whatever an access or volume named. A `places` setting at `/etc` with a caller's uid therefore handed it `/etc`. New `internal/apply/placement_guard.go`, judged before anything is applied; each refusal is a **failed resource with its reason** in the node's report (`PlacementRefusedError`, "… is not placed: … (novox/hq issue 339); nothing was touched"): 1. a directory, access or mount source that is, or holds, one of the machine's roots (`/`, `/etc`, `/usr`, `/var`, `/var/lib`, `/home`, `/run`, `/boot`, `/root`, `/proc`, `/sys`, `/dev`, `/var/lib/mesh`, …); 2. a directory or access in `/proc`, `/sys`, `/dev`, `/boot`, `/root`, or the engine's own trees (but its own module); a mount from `/boot`, `/root` or the engine's trees (kernel files, devices and the clock stay mountable: `systemPath` plumbing); 3. a non-root directory below `/etc`, `/usr`, `/run`; an access anywhere there; 4. below a home, a directory not owned by that home's account; 5. a container mounting any refused directory or access (it is not run). Every path is judged as declared and with links resolved. `applyDirectory`: `Lstat`; a directory whose last component is a link is refused. A directory that was there before this apply and that the mesh has no record of applying at this path is **used as found** (owner and mode left, said in the outcome, recorded `as_found`, never removed) — ADR 0182 beyond the home. Every directory on a running machine already has a record at its path, so nothing applied today changes. **Tests that fail on main** (run there first, guard-only test removed since it calls new functions): `TestNoDirectoryIsPlacedAtTheMachinesOwn`, `TestNoAccessIsAtTheMachinesOwn`, `TestNoContainerMountsTheMachinesOwn` (on main the container was run), `TestALinkIsNotFollowedToTheMachinesOwn` (on main the link's target was chmodded), `TestAFoundDirectoryIsUsedAsFound` (on main chmodded to 755). Plus `TestBelowAHomeOnlyThatAccountsDirectoryIsPlaced` and `TestAModulesOwnPlacesAreStillPlaced`. **Live check:** the guard was run (throwaway test, not committed) over the declarations `mesh-controller.plan` composes today for all four nodes — 356 directories, 96 containers, all accesses: nothing refused. Not taken from #61: the archive/`into` refusal below a `root: never` home (needs #61's `Root` field) and the home-itself refusal (the anchor's backup repository is placed directly under the homes' root; as-found covers a home). `merge-check.sh` passes locally. hq: issue 339 (PR to follow).
mesh-admin added 1 commit 2026-10-08 22:00:35 +00:00
Refuse a placement or mount at the machine's own trees, and use a found directory as found
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check fail: its merge-check.sh failed: --- FAIL: TestBelowAHomeOnlyThatAccountsDirectoryIsPlaced (0.00s)
3a002f6e7b
A module's places setting could point a directory anywhere, with an owner it
named, and the engine chowned and chmodded whatever it was pointed at as root,
through a link too; its accesses setting could mount any path into a container
(hq issue 339). The engine now refuses, as a failed resource with its reason,
a directory, access or mount source that is or holds one of the machine's
roots, anything placed in the kernel's, the boot loader's, root's or the
engine's own trees, a non-root directory below /etc, /usr or /run, an access
there, another account's directory below a home, and a container mounting
anything it refused, judged with every link resolved. A directory whose last
component is a link is refused, and one found here that the mesh did not make
keeps its owner and mode and is never removed.
Author
Contributor

Delivery novox/mesh-host@f39dbdbaf073 — delivered since 2026-10-08T22:40:16Z

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host

Machines

  • mesh-host on ace: passed — healthy 3 times over 2m28s
  • mesh-host on the rest running it: sent

Transitions

  • 2026-10-08 22:10 (new) → proposed (announced): novox/mesh-host#63's head announced
  • 2026-10-08 22:12 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 22:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-08 22:36 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-08 22:36 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
  • 2026-10-08 22:40 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-host@f39dbdbaf073` — **delivered** since 2026-10-08T22:40:16Z **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host **Machines** - mesh-host on ace: passed — healthy 3 times over 2m28s - mesh-host on the rest running it: sent **Transitions** - 2026-10-08 22:10 (new) → proposed (announced): novox/mesh-host#63's head announced - 2026-10-08 22:12 proposed → checked (checked): the verdict names this commit - 2026-10-08 22:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 22:36 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 22:36 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path - 2026-10-08 22:40 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at 3a002f6e

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
  • mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestBelowAHomeOnlyThatAccountsDirectoryIsPlaced (0.00s)

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host

Run by the build seat on g14 as build-1791496863759819599 (builds --log build-1791496863759819599).

--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T21:34:01Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-08T21:34:01Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.014s
ok  	github.com/novox/mesh-host/cmd/mesh-host	5.344s
ok  	github.com/novox/mesh-host/examples	1.034s
ok  	github.com/novox/mesh-host/internal/accounts	1.028s
--- FAIL: TestBelowAHomeOnlyThatAccountsDirectoryIsPlaced (0.00s)
    placement_homes_test.go:34: root's directory below alice's home was not refused as the machine's own: <nil>
FAIL
FAIL	github.com/novox/mesh-host/internal/apply	1.123s
ok  	github.com/novox/mesh-host/internal/bootstrap	1.313s
ok  	github.com/novox/mesh-host/internal/bundle	1.020s
ok  	github.com/novox/mesh-host/internal/declaration	1.045s
ok  	github.com/novox/mesh-host/internal/firewall	1.844s
ok  	github.com/novox/mesh-host/internal/identity	1.047s
ok  	github.com/novox/mesh-host/internal/image	1.018s
ok  	github.com/novox/mesh-host/internal/inventory	1.029s
ok  	github.com/novox/mesh-host/internal/link	10.353s
ok  	github.com/novox/mesh-host/internal/liveness	2.046s
ok  	github.com/novox/mesh-host/internal/network	1.035s
ok  	github.com/novox/mesh-host/internal/outward	1.022s
ok  	github.com/novox/mesh-host/internal/profile	1.531s
ok  	github.com/novox/mesh-host/internal/reachable	1.026s
ok  	github.com/novox/mesh-host/internal/store	1.094s
ok  	github.com/novox/mesh-host/internal/system	1.015s
ok  	github.com/novox/mesh-host/internal/tunnel	1.018s
ok  	github.com/novox/mesh-host/internal/units	1.014s
ok  	github.com/novox/mesh-host/internal/upgrade	1.038s
ok  	github.com/novox/mesh-host/internal/witness	1.576s
ok  	github.com/novox/mesh-host/packaging	1.013s
ok  	github.com/novox/mesh-host/validate	1.010s
FAIL
**Merge check** at `3a002f6e` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestBelowAHomeOnlyThatAccountsDirectoryIsPlaced (0.00s) **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host Run by the build seat on g14 as `build-1791496863759819599` (`builds --log build-1791496863759819599`). ``` --- the gate: mesh-host mesh-host: ok long-running resources without health: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T21:34:01Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-08T21:34:01Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-host --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.014s ok github.com/novox/mesh-host/cmd/mesh-host 5.344s ok github.com/novox/mesh-host/examples 1.034s ok github.com/novox/mesh-host/internal/accounts 1.028s --- FAIL: TestBelowAHomeOnlyThatAccountsDirectoryIsPlaced (0.00s) placement_homes_test.go:34: root's directory below alice's home was not refused as the machine's own: <nil> FAIL FAIL github.com/novox/mesh-host/internal/apply 1.123s ok github.com/novox/mesh-host/internal/bootstrap 1.313s ok github.com/novox/mesh-host/internal/bundle 1.020s ok github.com/novox/mesh-host/internal/declaration 1.045s ok github.com/novox/mesh-host/internal/firewall 1.844s ok github.com/novox/mesh-host/internal/identity 1.047s ok github.com/novox/mesh-host/internal/image 1.018s ok github.com/novox/mesh-host/internal/inventory 1.029s ok github.com/novox/mesh-host/internal/link 10.353s ok github.com/novox/mesh-host/internal/liveness 2.046s ok github.com/novox/mesh-host/internal/network 1.035s ok github.com/novox/mesh-host/internal/outward 1.022s ok github.com/novox/mesh-host/internal/profile 1.531s ok github.com/novox/mesh-host/internal/reachable 1.026s ok github.com/novox/mesh-host/internal/store 1.094s ok github.com/novox/mesh-host/internal/system 1.015s ok github.com/novox/mesh-host/internal/tunnel 1.018s ok github.com/novox/mesh-host/internal/units 1.014s ok github.com/novox/mesh-host/internal/upgrade 1.038s ok github.com/novox/mesh-host/internal/witness 1.576s ok github.com/novox/mesh-host/packaging 1.013s ok github.com/novox/mesh-host/validate 1.010s FAIL ```
jschoubben added 1 commit 2026-10-08 22:10:30 +00:00
Give the home test's account a uid of its own, so it holds when the suite runs as root
mesh/delivery delivered
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed
f39dbdbaf0
Author
Contributor

Merge check at f39dbdba

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
  • mesh/repo-check: PASS — its merge-check.sh passed

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host

Run by the build seat on shanks as build-1791497437489494863 (builds --log build-1791497437489494863).

--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T21:34:01Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-08T21:34:01Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.014s
ok  	github.com/novox/mesh-host/cmd/mesh-host	5.358s
ok  	github.com/novox/mesh-host/examples	1.019s
ok  	github.com/novox/mesh-host/internal/accounts	1.015s
ok  	github.com/novox/mesh-host/internal/apply	4.578s
ok  	github.com/novox/mesh-host/internal/bootstrap	1.657s
ok  	github.com/novox/mesh-host/internal/bundle	1.032s
ok  	github.com/novox/mesh-host/internal/declaration	1.082s
ok  	github.com/novox/mesh-host/internal/firewall	1.858s
ok  	github.com/novox/mesh-host/internal/identity	1.189s
ok  	github.com/novox/mesh-host/internal/image	1.044s
ok  	github.com/novox/mesh-host/internal/inventory	1.054s
ok  	github.com/novox/mesh-host/internal/link	10.330s
ok  	github.com/novox/mesh-host/internal/liveness	2.147s
ok  	github.com/novox/mesh-host/internal/network	1.112s
ok  	github.com/novox/mesh-host/internal/outward	1.046s
ok  	github.com/novox/mesh-host/internal/profile	1.541s
ok  	github.com/novox/mesh-host/internal/reachable	1.043s
ok  	github.com/novox/mesh-host/internal/store	1.276s
ok  	github.com/novox/mesh-host/internal/system	1.043s
ok  	github.com/novox/mesh-host/internal/tunnel	1.046s
ok  	github.com/novox/mesh-host/internal/units	1.040s
ok  	github.com/novox/mesh-host/internal/upgrade	1.204s
ok  	github.com/novox/mesh-host/internal/witness	4.788s
ok  	github.com/novox/mesh-host/packaging	1.043s
ok  	github.com/novox/mesh-host/validate	1.037s
**Merge check** at `f39dbdba` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host Run by the build seat on shanks as `build-1791497437489494863` (`builds --log build-1791497437489494863`). ``` --- the gate: mesh-host mesh-host: ok long-running resources without health: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T21:34:01Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-08T21:34:01Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-host --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.014s ok github.com/novox/mesh-host/cmd/mesh-host 5.358s ok github.com/novox/mesh-host/examples 1.019s ok github.com/novox/mesh-host/internal/accounts 1.015s ok github.com/novox/mesh-host/internal/apply 4.578s ok github.com/novox/mesh-host/internal/bootstrap 1.657s ok github.com/novox/mesh-host/internal/bundle 1.032s ok github.com/novox/mesh-host/internal/declaration 1.082s ok github.com/novox/mesh-host/internal/firewall 1.858s ok github.com/novox/mesh-host/internal/identity 1.189s ok github.com/novox/mesh-host/internal/image 1.044s ok github.com/novox/mesh-host/internal/inventory 1.054s ok github.com/novox/mesh-host/internal/link 10.330s ok github.com/novox/mesh-host/internal/liveness 2.147s ok github.com/novox/mesh-host/internal/network 1.112s ok github.com/novox/mesh-host/internal/outward 1.046s ok github.com/novox/mesh-host/internal/profile 1.541s ok github.com/novox/mesh-host/internal/reachable 1.043s ok github.com/novox/mesh-host/internal/store 1.276s ok github.com/novox/mesh-host/internal/system 1.043s ok github.com/novox/mesh-host/internal/tunnel 1.046s ok github.com/novox/mesh-host/internal/units 1.040s ok github.com/novox/mesh-host/internal/upgrade 1.204s ok github.com/novox/mesh-host/internal/witness 4.788s ok github.com/novox/mesh-host/packaging 1.043s ok github.com/novox/mesh-host/validate 1.037s ```
mesh-admin merged commit a2c2c35e85 into main 2026-10-08 22:36:46 +00:00
mesh-admin deleted branch fix/339-the-engine-places-nothing-in-the-machines-own-trees 2026-10-08 22:36:46 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-host#63