Why SSH is central to a Raspberry Pi homelab
Many Raspberry Pi builds run without a permanently attached screen or keyboard. SSH becomes the maintenance channel for updating software, deploying services and investigating problems. That convenience makes remote access both essential and easy to break with one mistaken policy change.
The official Raspberry Pi operational security documentation recommends considering firewall controls and improving SSH with key-based authentication. Its remote-access guide documents SSH key-pair setup and Ed25519 options.
Four sensible layers for a home gateway
Key-based identity
Create a protected SSH key on a trusted client, install only its public key on the Pi, and verify an independent new session before changing password-authentication rules. Keep the private key private and use a passphrase appropriate to your threat model.
Source-network policy
Know whether you connect from a home LAN, an actual VPN source address, or another path. UFW rules must match the addresses your gateway actually sees. For example, a private VPN subnet and a local network subnet are not interchangeable just because both are 'trusted' environments. Do not enable a restrictive policy until the needed access path is permitted and tested.
Recovery and backup
Protect a recovery identity independently of the main workstation and practice the restore procedure while you still have working access. Ordinary USB storage can be suitable as one encrypted backup medium if its reliability, security and handling are managed. An offline backup is only as good as the ability to unlock and use it.
Observable proof
Measure the end state: new SSH authentication succeeds using the intended key, effective server settings match the policy, and source-network controls behave as expected. Include a negative test from a non-authorized source when practical. Configuration files alone are not proof of actual network behavior.
Where XSSG fits—and where it does not yet
XSSG's documented beta demonstrates a guided macOS-to-Linux SSH/UFW workflow, including encrypted USB recovery and independent login checks. That model is relevant to single-board computers, mini PCs, NAS boxes and edge projects, but Raspberry Pi OS and Jetson Orin Nano board-specific compatibility are not yet verified claims. Hardware-specific testing must establish supported distributions, architectures, services and recovery paths.
The related builder documentation describes the vault and verification concepts. The security evidence page makes clear which fault-injection and alternate-network tests remain incomplete.
FIDO2 SSH enrollment and Mosh are planned future features. Neither should be assumed available on Raspberry Pi or any other XSSG target today. Public downloads are Coming Soon.
A sensible next step for makers
Read the Raspberry Pi Foundation's current operating-system documentation, practice on a noncritical test host, and keep local access available until you have demonstrated recovery. From there, explore SSH lockout prevention, encrypted USB backup design, and the XSSG seven-stage method.
Primary sources
Raspberry Pi remote access · Raspberry Pi operational security · Ubuntu OpenSSH service guidance.
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 →Encrypted SSH key backup
Understand per-gateway vaults, secret separation and restoration proof
Read this guide →