Show how far the setuid search got, and start a fresh one when the terminal asks (hq issue 361) #76

Merged
mesh-admin merged 2 commits from fix/361-the-setuid-search-shows-its-progress into main 2026-10-10 00:21:52 +00:00
Contributor

hq issue 361 (the control-node's agent account is never judged).

  1. Progress visible. At each checkpoint (once a minute) the walk's progress is snapshotted in memory, with no extra I/O. The snapshot holds filesystems done/total, the mount point being walked, entries visited, setuid/setgid-root files found so far, when it was last kept, and how long each finished filesystem took (time spent walking only). The account verdict carries it as search fields on the account's resource health, and its reason gains one progress: line that the controller's root-free repeats. It is kept outside the verdict's change detection, so the journal does not repeat it every minute. It never names the cursor or a found path. Entries are counted once across a resume, because the count is kept with the cursor it matches.
  2. A fresh search on ask. mesh.node.<node>.ask.setuid-search is a signed ask, checked exactly as a hand-over is (shared believed) but under its own signing context novox-mesh setuid-search v1. On it, the engine throws away the last complete search (kept and in memory) and any walk under way or kept. It cancels a running walk. The next look then starts a full search. It is terminal-only: see the hq record.

Controlled by mesh-controller's node setuid-search <node> (companion PR), which also grants the subject. Roll the controller out first, so the bus grant exists before the engine subscribes.

Tests: internal/accounts/setuid_progress_test.go, internal/link/setuid_search_test.go, and cmd/mesh-host TestTheStatementSaysHowFarTheSetuidSearchGot. merge-check.sh passes locally.

hq issue 361 (the control-node's agent account is never judged). 1. **Progress visible.** At each checkpoint (once a minute) the walk's progress is snapshotted in memory, with no extra I/O. The snapshot holds filesystems done/total, the mount point being walked, entries visited, setuid/setgid-root files found so far, when it was last kept, and how long each finished filesystem took (time spent walking only). The account verdict carries it as `search` fields on the account's resource health, and its reason gains one `progress:` line that the controller's `root-free` repeats. It is kept outside the verdict's change detection, so the journal does not repeat it every minute. It never names the cursor or a found path. Entries are counted once across a resume, because the count is kept with the cursor it matches. 2. **A fresh search on ask.** `mesh.node.<node>.ask.setuid-search` is a signed ask, checked exactly as a hand-over is (shared `believed`) but under its own signing context `novox-mesh setuid-search v1`. On it, the engine throws away the last complete search (kept and in memory) and any walk under way or kept. It cancels a running walk. The next look then starts a full search. It is terminal-only: see the hq record. Controlled by mesh-controller's `node setuid-search <node>` (companion PR), which also grants the subject. Roll the controller out first, so the bus grant exists before the engine subscribes. Tests: `internal/accounts/setuid_progress_test.go`, `internal/link/setuid_search_test.go`, and `cmd/mesh-host` TestTheStatementSaysHowFarTheSetuidSearchGot. merge-check.sh passes locally.
mesh-admin added 1 commit 2026-10-09 23:56:14 +00:00
Show how far the setuid search got, and start a fresh one when the terminal asks (hq issue 361)
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: TestNatsAnEnrolmentWithNoReplyAddressIsNotAnswered (0.00s)
mesh/delivery superseded: a newer head of the same pull request
8e79403c21
The walk kept its progress every minute and nobody could read it: root-free said only that a search ran.
The account verdict now carries the progress (counts, times, mount points; never a path) as fields and in
its reason, outside what makes a verdict changed. A signed ask from the controller's terminal throws the last
search away and starts a full one, after the operator removed by hand what it found.
Author
Contributor

Delivery novox/mesh-host@0b4c86e3bed4 — delivered since 2026-10-10T00:25:35Z

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 2m24s
  • mesh-host on the rest running it: sent

Transitions

  • 2026-10-10 00:00 (new) → proposed (announced): novox/mesh-host#76's head announced
  • 2026-10-10 00:02 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 00:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 00:22 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-10 00:22 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-10 00:25 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@0b4c86e3bed4` — **delivered** since 2026-10-10T00:25:35Z **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 2m24s - mesh-host on the rest running it: sent **Transitions** - 2026-10-10 00:00 (new) → proposed (announced): novox/mesh-host#76's head announced - 2026-10-10 00:02 proposed → checked (checked): the verdict names this commit - 2026-10-10 00:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 00:22 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 00:22 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-10 00:25 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 8e79403c

  • 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: TestNatsAnEnrolmentWithNoReplyAddressIsNotAnswered (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-1791590204069140742 (builds --log build-1791590204069140742).

--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 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-09T23:50:31Z 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-09T23:50:31Z

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.011s
ok  	github.com/novox/mesh-host/cmd/mesh-host	5.610s
ok  	github.com/novox/mesh-host/examples	1.015s
ok  	github.com/novox/mesh-host/internal/accounts	1.358s
ok  	github.com/novox/mesh-host/internal/apply	2.466s
ok  	github.com/novox/mesh-host/internal/bootstrap	1.372s
ok  	github.com/novox/mesh-host/internal/bundle	1.011s
ok  	github.com/novox/mesh-host/internal/declaration	1.047s
ok  	github.com/novox/mesh-host/internal/firewall	1.829s
ok  	github.com/novox/mesh-host/internal/identity	1.042s
ok  	github.com/novox/mesh-host/internal/image	1.014s
ok  	github.com/novox/mesh-host/internal/inventory	1.017s
--- FAIL: TestNatsAnEnrolmentWithNoReplyAddressIsNotAnswered (0.00s)
    asking_nats_test.go:124: consumer is already bound to a subscription
FAIL
FAIL	github.com/novox/mesh-host/internal/link	9.505s
ok  	github.com/novox/mesh-host/internal/liveness	2.046s
ok  	github.com/novox/mesh-host/internal/meshcli	1.348s
ok  	github.com/novox/mesh-host/internal/network	1.042s
ok  	github.com/novox/mesh-host/internal/outward	1.029s
ok  	github.com/novox/mesh-host/internal/profile	1.522s
ok  	github.com/novox/mesh-host/internal/reachable	1.030s
ok  	github.com/novox/mesh-host/internal/store	1.094s
ok  	github.com/novox/mesh-host/internal/system	1.011s
ok  	github.com/novox/mesh-host/internal/tunnel	1.017s
ok  	github.com/novox/mesh-host/internal/units	1.010s
ok  	github.com/novox/mesh-host/internal/upgrade	1.042s
ok  	github.com/novox/mesh-host/internal/witness	1.505s
ok  	github.com/novox/mesh-host/packaging	1.009s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.011s
FAIL
**Merge check** at `8e79403c` - `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: TestNatsAnEnrolmentWithNoReplyAddressIsNotAnswered (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-1791590204069140742` (`builds --log build-1791590204069140742`). ``` --- the gate: mesh-host mesh-host: ok long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 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-09T23:50:31Z 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-09T23:50:31Z 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.011s ok github.com/novox/mesh-host/cmd/mesh-host 5.610s ok github.com/novox/mesh-host/examples 1.015s ok github.com/novox/mesh-host/internal/accounts 1.358s ok github.com/novox/mesh-host/internal/apply 2.466s ok github.com/novox/mesh-host/internal/bootstrap 1.372s ok github.com/novox/mesh-host/internal/bundle 1.011s ok github.com/novox/mesh-host/internal/declaration 1.047s ok github.com/novox/mesh-host/internal/firewall 1.829s ok github.com/novox/mesh-host/internal/identity 1.042s ok github.com/novox/mesh-host/internal/image 1.014s ok github.com/novox/mesh-host/internal/inventory 1.017s --- FAIL: TestNatsAnEnrolmentWithNoReplyAddressIsNotAnswered (0.00s) asking_nats_test.go:124: consumer is already bound to a subscription FAIL FAIL github.com/novox/mesh-host/internal/link 9.505s ok github.com/novox/mesh-host/internal/liveness 2.046s ok github.com/novox/mesh-host/internal/meshcli 1.348s ok github.com/novox/mesh-host/internal/network 1.042s ok github.com/novox/mesh-host/internal/outward 1.029s ok github.com/novox/mesh-host/internal/profile 1.522s ok github.com/novox/mesh-host/internal/reachable 1.030s ok github.com/novox/mesh-host/internal/store 1.094s ok github.com/novox/mesh-host/internal/system 1.011s ok github.com/novox/mesh-host/internal/tunnel 1.017s ok github.com/novox/mesh-host/internal/units 1.010s ok github.com/novox/mesh-host/internal/upgrade 1.042s ok github.com/novox/mesh-host/internal/witness 1.505s ok github.com/novox/mesh-host/packaging 1.009s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.011s FAIL ```
jschoubben added 1 commit 2026-10-10 00:00:12 +00:00
Count a setuid find only where the account can execute it, read at every judgement (hq issue 361)
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
mesh/delivery delivered
0b4c86e3be
The two finds on the control-node sit in the operator's home of mode 0700, which the agent account cannot
search. The search keeps every find; each judgement reads the modes on the way again, since an account can
open its own home without root. A find in a home is said by count, its path in the journal alone. Also
from review: a checkpoint racing SearchNow forgets the walk it just kept, and a walk kept by an older engine
says its counts as lower bounds.
Author
Contributor

Merge check at 0b4c86e3

  • 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-1791590419487540657 (builds --log build-1791590419487540657).

--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 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-09T23:50:31Z 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-09T23:50:31Z

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.016s
ok  	github.com/novox/mesh-host/cmd/mesh-host	5.605s
ok  	github.com/novox/mesh-host/examples	1.024s
ok  	github.com/novox/mesh-host/internal/accounts	1.470s
ok  	github.com/novox/mesh-host/internal/apply	4.856s
ok  	github.com/novox/mesh-host/internal/bootstrap	1.635s
ok  	github.com/novox/mesh-host/internal/bundle	1.039s
ok  	github.com/novox/mesh-host/internal/declaration	1.079s
ok  	github.com/novox/mesh-host/internal/firewall	1.873s
ok  	github.com/novox/mesh-host/internal/identity	1.128s
ok  	github.com/novox/mesh-host/internal/image	1.039s
ok  	github.com/novox/mesh-host/internal/inventory	1.039s
ok  	github.com/novox/mesh-host/internal/link	10.464s
ok  	github.com/novox/mesh-host/internal/liveness	2.082s
ok  	github.com/novox/mesh-host/internal/meshcli	1.358s
ok  	github.com/novox/mesh-host/internal/network	1.065s
ok  	github.com/novox/mesh-host/internal/outward	1.048s
ok  	github.com/novox/mesh-host/internal/profile	1.530s
ok  	github.com/novox/mesh-host/internal/reachable	1.043s
ok  	github.com/novox/mesh-host/internal/store	1.239s
ok  	github.com/novox/mesh-host/internal/system	1.046s
ok  	github.com/novox/mesh-host/internal/tunnel	1.051s
ok  	github.com/novox/mesh-host/internal/units	1.038s
ok  	github.com/novox/mesh-host/internal/upgrade	1.179s
ok  	github.com/novox/mesh-host/internal/witness	4.940s
ok  	github.com/novox/mesh-host/packaging	1.038s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.034s
**Merge check** at `0b4c86e3` - `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-1791590419487540657` (`builds --log build-1791590419487540657`). ``` --- the gate: mesh-host mesh-host: ok long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 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-09T23:50:31Z 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-09T23:50:31Z 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.016s ok github.com/novox/mesh-host/cmd/mesh-host 5.605s ok github.com/novox/mesh-host/examples 1.024s ok github.com/novox/mesh-host/internal/accounts 1.470s ok github.com/novox/mesh-host/internal/apply 4.856s ok github.com/novox/mesh-host/internal/bootstrap 1.635s ok github.com/novox/mesh-host/internal/bundle 1.039s ok github.com/novox/mesh-host/internal/declaration 1.079s ok github.com/novox/mesh-host/internal/firewall 1.873s ok github.com/novox/mesh-host/internal/identity 1.128s ok github.com/novox/mesh-host/internal/image 1.039s ok github.com/novox/mesh-host/internal/inventory 1.039s ok github.com/novox/mesh-host/internal/link 10.464s ok github.com/novox/mesh-host/internal/liveness 2.082s ok github.com/novox/mesh-host/internal/meshcli 1.358s ok github.com/novox/mesh-host/internal/network 1.065s ok github.com/novox/mesh-host/internal/outward 1.048s ok github.com/novox/mesh-host/internal/profile 1.530s ok github.com/novox/mesh-host/internal/reachable 1.043s ok github.com/novox/mesh-host/internal/store 1.239s ok github.com/novox/mesh-host/internal/system 1.046s ok github.com/novox/mesh-host/internal/tunnel 1.051s ok github.com/novox/mesh-host/internal/units 1.038s ok github.com/novox/mesh-host/internal/upgrade 1.179s ok github.com/novox/mesh-host/internal/witness 4.940s ok github.com/novox/mesh-host/packaging 1.038s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.034s ```
mesh-admin merged commit cc0b8554b1 into main 2026-10-10 00:21:52 +00:00
mesh-admin deleted branch fix/361-the-setuid-search-shows-its-progress 2026-10-10 00:21:52 +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#76