Start here: what XSSG is
XSSG v0.9.9-beta16 is a locally guided macOS-to-Linux SSH security workflow. It examines an existing OpenSSH gateway, verifies key-only access, prepares an exact SSH/UFW plan, creates an encrypted USB recovery vault, requires an independent restore/login test for guided hardening, and verifies the result before committing. It is not a central SSH proxy, hardware key vendor, or FIDO2 enrollment product today.
1. Requirements and scope
Tested workflow: a Mac controller running the terminal wizard, an accessible Linux SSH server using OpenSSH and compatible systemd and UFW, SSH administrator credentials, and a user-provided mounted USB drive for encrypted recovery. Verify sudo rights, network routes, and Linux distribution compatibility first. FIDO2 enrollment remains on the roadmap.
2. Launch and choose the gateway
cd ~/X/xerxes_ssh_wizard
bash xerxes-ssh.shThe guided mode offers the last-used gateway or entry of another Linux host. A saved profile is only a convenience, never proof that the gateway is currently secure. XSSG checks reachability, host-key context, SSH key format and a fresh key-based login.
3. Review authorized networks
Specify the LAN/VPN networks that must reach the SSH port; example CIDRs such as 192.168.1.0/24 and 10.8.0.0/24 are illustrations, not safe defaults for everyone. The wizard checks the current client source against the planned allowlist, then produces a read-only UFW/SSH before-versus-after comparison. Unrelated services should not be modified by the SSH-scoped transaction.
4. Make the vault on your own USB drive
Select the mounted USB. XSSG uses /X/vault/ for encrypted .xkv files and /X/xerxes_ssh_wizard/ for the portable program. New-format vaults contain an identification header plus an authenticated encrypted payload. The vault password is independent of the SSH private-key passphrase. Save each recovery password separately from the USB; without it there is no supported password reset.
5. Verify before you alter access
Restore a selected encrypted vault into a new key file without replacing the working key. The system proves that exact restored key can authenticate to the target server without falling back to account passwords. Repeated password prompts are expected because encryption, private-key unlocking and separate privileged Linux sessions are distinct checks.
6. Review, apply, verify, commit
- Confirm the existing SSH key works.
- Collect read-only server evidence and prepare exact UFW/SSH changes.
- Create or reuse an encrypted vault, then independently restore and authenticate.
- Arm a server-side five-minute emergency rollback using systemd before mutating security settings.
- Install/verify approved UFW SSH source rules before altering effective SSH password authentication.
- Open a fresh public-key-only SSH connection and verify the effective SSH and UFW policies.
- Cancel the rollback timer only on explicit confirmed success.
The timer is a safeguard, not a substitute for having out-of-band console access. If verification fails or the controller loses access, recovery is attempted through the independent timer; that failure path still needs controlled physical-environment validation.
7. Selective recovery and key rotation
One USB may hold several encrypted keys. Installing the XSSG program imports zero SSH keys. Explicitly restoring one vault installs only the chosen key. A valid matching vault can be reused; rotated-key replacement requires explicit selection and authentication. Older root-level vaults are available only through deliberate legacy recovery browsing, not normal automatic matching.
8. What the final receipt proves
Receipts record the observed SSH key fingerprint, key-login proof, effective SSH policy, UFW source-rule state, protected transaction status, USB restore proof, and paths that were not independently tested. A local LAN proof does not validate the VPN path or public-internet exposure. The default workflow does not claim third-party certification.
9. USB layout
/X/
START_HERE.txt
vault/
your-selected-key.xkv
xerxes_ssh_wizard/
xerxes-ssh.sh
scripts/Legacy program recovery directories may exist from previous beta upgrades; review them before cleanup rather than erasing unfamiliar files.
10. Recovery and troubleshooting
For a failed key-only login, stop before hardening and verify the server, account, selected key, and allowed source address. If the USB is not detected, inspect its mount path before performing any writes. If rollback status is uncertain, use a trusted server console or independent administration path and review the transaction journal. Never delete the only known-good vault while investigating.
11. Primary documentation
OpenSSH manuals · age encryption · systemd-run · Ubuntu FIDO guidance · OSSTMM. See current limitations before using XSSG on a high-consequence production system.
Keep exploring
The encrypted vault · The recovery-first method · Operational manual · Q&A · Tools that complement XSSG · The wider XERXES SI story