Circuit-Forge/cf-node-bootstrap
6
0
Fork 0
Code Issues 10 Pull requests Projects Releases Packages Wiki Activity Actions

Orchard-join: WireGuard/autossh coordinator connection + secure adoption flow (2FA) #10

New issue
Open
opened 2026-07-18 23:25:45 -07:00 by pyr0ball · 0 comments
pyr0ball commented 2026-07-18 23:25:45 -07:00
Owner
Copy link

Currently orchard-join nodes connect to the coordinator via a plain HTTP URL (e.g. CF_COORDINATOR_URL=http://10.1.10.71:7700) with no tunneling or authenticated pairing. Need a WireGuard/autossh-based secure connection option, plus an adoption flow: the coordinator generates a short-lived link/token during setup, the joining node authenticates against it with a 2FA prompt before being trusted.

Spans two repos:

  • cf-node-bootstrap: the orchard-join flow (provisioning.run_orchard_profile in the Python cutover) consumes the adoption link and sets up the tunnel
  • circuitforge-orch: the coordinator side needs to generate adoption links + verify the 2FA challenge

Needs its own brainstorm/spec - deliberately not folded into the bash-to-python-cutover-design.md spec (which only covers today's plain-URL orchard-join), raised during Phase 1 implementation on 2026-07-18.

Currently orchard-join nodes connect to the coordinator via a plain HTTP URL (e.g. CF_COORDINATOR_URL=http://10.1.10.71:7700) with no tunneling or authenticated pairing. Need a WireGuard/autossh-based secure connection option, plus an adoption flow: the coordinator generates a short-lived link/token during setup, the joining node authenticates against it with a 2FA prompt before being trusted. Spans two repos: - cf-node-bootstrap: the orchard-join flow (provisioning.run_orchard_profile in the Python cutover) consumes the adoption link and sets up the tunnel - circuitforge-orch: the coordinator side needs to generate adoption links + verify the 2FA challenge Needs its own brainstorm/spec - deliberately not folded into the bash-to-python-cutover-design.md spec (which only covers today's plain-URL orchard-join), raised during Phase 1 implementation on 2026-07-18.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/cf-node-bootstrap#10
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?