ssh: keep eta ssh recoverable and automate topology docs - #722
Merged
Conversation
mulatta
force-pushed
the
fix-eta-ssh-access
branch
from
August 22, 2026 16:21
15ffd8a to
0d09972
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.
This keeps eta's public SSH endpoint reliable as a WireGuard-independent recovery path by replacing sequential connection rate limits with OpenSSH concurrency controls and key-only authentication, standardizing FQDN-based ProxyJump configuration and host certificates, and adding repeatable hardware, LLDP, and Nix-derived network topology documentation. Verification covered Nix parsing, evaluation, and formatting; Bash syntax and ShellCheck; Ruff, mypy, and unit tests; ssh -G; generator freshness; and live host and LLDP collection.