What does SSH key management actually include?
An SSH key pair has two different jobs. The private key remains under the operator’s control; the corresponding public key can be authorized on a server. Creating that pair is important, but it is only the start. A real operating plan must address where the private key lives, who can use it, which servers trust it, how access is reviewed, and what happens if a laptop or recovery copy disappears.
NIST IR 7966 treats SSH as an access-management problem, not merely a command-line convenience. Strong key management includes governance over trust relationships and their lifecycle. That is the context for XSSG's narrower design goal: make an individual operator's high-risk setup and recovery steps consistent.
A guided, recovery-first SSH workflow
The documented XSSG beta begins with inspection rather than an immediate configuration rewrite. It checks the selected gateway, examines the relevant SSH and firewall state, and asks the operator to review authorized source networks. Before restrictive changes, the workflow verifies that a protected recovery key can actually authenticate from a separate path.
- Identify the gateway. Confirm which server, SSH port, account and access route are being changed.
- Protect the identity. Use key-based authentication and separate the SSH private-key passphrase from the encryption password protecting its recovery vault.
- Prove recovery. Restore the selected key from encrypted media and confirm it can connect independently.
- Prepare rollback. Stage a timed recovery mechanism before firewall and SSH changes.
- Apply, then verify. Review changes, test effective configuration, and establish a fresh connection before committing.
Read the current operator manual for the implementation detail and security claims page for what has and has not yet been demonstrated. XSSG is not an enterprise SSH certificate authority, a bastion proxy, or a replacement for ongoing key inventory across thousands of hosts.
How is this different from an SSH key vault or agent?
A password manager with an SSH agent can simplify secure storage and signing. Bitwarden, for example, provides an encrypted SSH key workflow. Smallstep focuses on short-lived SSH certificates and identity-based access. Teleport addresses broader managed infrastructure access. These are valuable approaches, serving different operational needs.
XSSG's current story is the setup transaction itself: check the server, safeguard a recoverable key, establish a rollback path, and verify what changed. The products may complement one another. Visit the tool landscape to choose by use case rather than by marketing category.
What about key rotation, passphrases and backups?
Key rotation is a trust transition, not just generating a new file. The new public key must be authorized, the old key's reach must be understood, and removal should not happen until the replacement has been tested. A passphrase protects an individual private key; an encrypted USB recovery vault protects a backup copy. These secrets should not be confused or automatically reused.
XSSG documents selective restoration and a recovery-first sequence in its beta. Hardware failure testing, platform qualification and a complete independent assessment remain outstanding. A checksum can detect accidental or deliberate byte changes when compared against a trusted reference, but a checksum by itself does not authenticate the release publisher.
The product's public release is Coming Soon. FIDO2-backed SSH enrollment and Mosh support are planned, not currently shipping. No special XERXES USB hardware is required.
When should you look at XSSG?
If you administer a Linux gateway from a Mac, want to learn exactly what your hardening workflow changes, and care about returning safely after an error, XSSG is designed around that problem. Larger fleets, centralized identity providers and production compliance programs may require additional infrastructure-management tools. Start with the technical model, inspect the vault design, then assess the evidence before deployment.
Primary documentation
NIST IR 7966: SSH access management · OpenSSH ssh-keygen · OpenSSH sshd verification.
Explore the system, not just the slogan.
See the operator manual, documented security limits, complementary tools, and the Coming Soon release page.
Prevent SSH lockout
A reversible sequence for risky SSH and firewall changes
Read this guide →Encrypted SSH key backup
Understand per-gateway vaults, secret separation and restoration proof
Read this guide →Raspberry Pi SSH security
Key-first homelab security without invented board support
Read this guide →