Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2724

A node without a route to the site takes the archive from a peer and still verifies it itself

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
safe-self-update
Milestone status
ACTIVE
Wave
1
Waiting on
I2720
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI2720I2720 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2724

majordomus plan verify I2724

majordomus plan done I2724

What it is

Objective
Let a following node that cannot reach github.com or majordomus.dev fetch the release archive from a linked peer over the authenticated mesh link, and install it only after checking its digest and size against release metadata it read itself or that was relayed and signed by the publishing node.
Why
ADR 0161. jetson has no route to github.com; on 2026-10-14 its v0.25.0 archive was copied over the LAN by hand.
Now
A node without a route to the site is upgraded by copying an archive to it by hand.
Wanted
self update --apply on such a node asks a linked peer for the archive and the metadata, verifies before unpacking, and installs through the same installer path; a mismatch is refused and reported on the board.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • A node with no route to the site upgrades from a peer's archive and verifies it before unpacking
  • A peer archive whose digest differs from the metadata is refused and reported
Validation
bin/majordomus plan validateMJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>
Evidence required
relayed_archive_verified_test
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/meshapps/majordomus-cli/src/releasesite/static/install.shdocs/MESH.mdtest/cases
Not
Trusting a digest a peer sends without metadata the node can verify
Depends on
I2720I2165
Priority
p1
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-14
Updated
2026-10-14
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.