Why carry an encrypted SSH recovery USB?
An SSH key can outlive the laptop that usually holds it. Hardware failure, accidental deletion, compromised endpoints and forgotten setup details can interrupt an otherwise healthy service. A removable recovery copy gives an operator a different path back, provided the media is protected, the secret is known, and the restored identity has been verified against the intended server.
The XSSG concept uses ordinary compatible USB storage. The premium black-metal stick shown on the site is artwork, not hardware manufactured or sold by XERXES SI. The value proposition is the reproducible recovery procedure, not the material of the casing.
What is an XSSG .xkv vault file?
The documented format uses a selected .xkv file for an individual gateway recovery record. Public identification metadata helps an operator select the intended vault without exposing the encrypted recovery payload. Each selected vault can have its own encryption password, rather than relying on one universal secret across every gateway.
The vault password protects the stored recovery payload. The passphrase on an SSH private key protects that key itself. These are different controls, and treating them as separate is useful: compromise of one credential should not automatically imply that all security boundaries have disappeared. The real protection depends on encryption strength, password quality, how the secrets are handled, and the security of the machine doing the recovery.
Backup existence is not recovery proof
Being able to read a file from a USB drive establishes only that some bytes are present. A meaningful drill confirms the chosen file can be opened with its vault password, that the expected key material can be restored, and that the resulting private key can complete a new SSH authentication to the intended host. This is the difference between a file backup and an access-recovery test.
XSSG documents an independent recovered-key login check before proceeding to restrictive SSH changes. That sequence is worth learning even outside the XSSG software: verify recoverability before dependence on the recovery path becomes urgent.
What does SHA-256 verify—and what doesn't it?
A SHA-256 checksum is a compact digest for checking whether the bytes of a file match a known reference. It is useful for accidental corruption detection and reproducible release verification. But if an attacker can replace both the file and its checksum, the two can still agree. A checksum alone is not a digital signature, identity proof or publisher authentication mechanism.
Authenticated encryption is another distinct layer: it can help detect unauthorized alterations to encrypted data during decryption. Neither a checksum nor vault encryption establishes that an operator can successfully log in after restoring the recovered key. The independent connection test supplies that missing operational proof.
The current software uses your removable storage for an encrypted recovery vault. FIDO2 hardware-backed SSH authentication is a planned future capability, not a shipping feature, and the FIDO2 concept illustration should not be mistaken for a current XERXES hardware product.
Recovery habits worth keeping
Use strong unique secrets, restrict who may access the removable media, document which gateway each vault belongs to without publishing private details, and keep a separate recovery route that can still be used when your normal workstation is unavailable. Avoid keeping the only backup in the same failure domain as the original key. Periodically verify a restoration in a safe, authorized environment.
Before choosing an XSSG build, read the test limits. The current documentation notes that media compatibility, interrupted writes and failure recovery have not all been independently qualified.
Technical reading
OpenSSH key format and passphrases · age encrypted file tooling · XSSG vault and verification model.
Explore the system, not just the slogan.
See the operator manual, documented security limits, complementary tools, and the Coming Soon release page.
SSH key management
From the first key to independently verified recovery
Read this guide →Prevent SSH lockout
A reversible sequence for risky SSH and firewall changes
Read this guide →Raspberry Pi SSH security
Key-first homelab security without invented board support
Read this guide →