Repository navigation
feat(ssh): support the server as an encrypted relay participant - #345
Open
theogravity wants to merge 2 commits into
Open
theogravity wants to merge 2 commits into
theogravity wants to merge 2 commits into
Conversation
theogravity
force-pushed
the
feat/ssh-wizard
branch
from
October 11, 2026 08:48
21a9383 to
aa26599
Compare
theogravity
force-pushed
the
feat/ssh-server-relay
branch
from
October 11, 2026 08:48
7ed6098 to
a14e32d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SSH sessions can now use the server or an enrolled node as either the connecting machine or the source of selected SSH agent keys. Both paths use the same encrypted relay runtime and existing machine launch permissions.
The server has a dedicated persistent relay identity, explicit admin recovery, peer trust management, and backup coverage. Relay cleanup covers shutdown and permission changes; setup-here retains the exact selected keys. Shared pin storage also refuses repeated first-use after quarantining a corrupt trust file.
Stacked on #344.
Validation: full workspace tests, TypeScript checks, lint and license checks; real encrypted relay tests in both directions, selected-key filtering, identity races/recovery, backup roundtrip and socket cleanup. Final node suite: 1,109 passed. Independent review passed with no outstanding findings.