The Defend-O-Tron has a built-in remote support feature. You start a session from the admin terminal, our support engineers connect for as long as the session lasts, and the session ends the moment you press Enter on the terminal. The tunnel is never open unless you opened it.
The Defend-O-Tron only maintains a support connection until you end it by pressing Enter at the prompt. Pressing Enter tears down both the SSH session and the underlying WireGuard tunnel. This design keeps your device secured and is never active unless you initiate the connection.
A few quick checks:
Awesome-O technicians will never ask for your password. WireGuard public keys are considered public; you can send them to support technicians in plain text without security concerns. Your private keys never leave the device.
tech-support. You'll be prompted for your admin password.What a successful start looks like:
admin@defend-o-tron: tech-support
[sudo] password for admin:
Support account will expire on 2026-05-16 (Etc/UTC)
OK Success support user account
OK Success creating wireguard interface wg0
Public Key: [ VFZ9XaE+V08XnoIaEtUGlAzzk2NLoQ43Zxyag+gfcik= ] for remote server
[+] Running 2/2
✔ Network wgnet Created 0.1s
✔ Container support Started 1.3s
Press enter to exit support mode...
The
tech-supportcommand has a built-in timeout if it can't connect to the support server. If the connection takes too long, end the session and try again — usually a firewall or DNS issue. Check your firewall allows outbound TCP 60.
Press Enter in the terminal where tech-support is running. The Defend-O-Tron:
[+] Running 2/2
✔ Container support Removed 0.7s
✔ Network wgnet Removed 0.0s
OK Success removing wireguard wg0
admin@defend-o-tron:
That's it. The tunnel is gone, the SSH access path is closed, and the device is back to its normal state.
Each time you run tech-support, the device generates a fresh WireGuard keypair and creates a temporary support account that only accepts SSH connections over the WireGuard tunnel. The support team has the matching public key on their side; they SSH in over the tunnel using a strictly-scoped key for diagnostics. When you press Enter to end the session, the tunnel collapses immediately, the account is locked, and the keys are not reused.
Want the full protocol detail? The remote-support tooling lives in the
awesome-o-remote-supportpackage; the design document covering planned changes (per-device static keys, server-side enrollment) is part of the packaging documentation. Contact support for a copy if you need it for an audit or security review.
tech-support session is logged and captured by the daily signed manifest.