Repository navigation
Remote Operation
The remote access guide is the authoritative procedure. The base container exposes no ports; SSH requires its explicit overlay and a protected, existing public-key file. Never put client private keys in the image or repository.
| Task | Guide |
|---|---|
| Enable key-only SSH and loopback binding | Authorized keys |
| Verify server fingerprint and understand key rotation | Host identity |
| Reach a trusted VPN/private interface | Remote clients |
| Rejoin work and observe a session | tmux |
| Forward an OAuth callback safely | Restricted forwarding |
| Inspect effective server settings | Effective configuration |
| Diagnose connection problems privately | Troubleshooting and diagnostics |
Phone/tablet use requires a protected SSH key, trusted host fingerprint, a private network path and a workable terminal/tmux keyboard. The project does not supply a VPN, mobile app or certified client matrix.
Read-only tmux attachment limits input through that client, but a shared dev shell is fully capable of modifying files and reading account state. It is not a viewer authorization role.
Only the selected loopback callback destination is permitted. A local SSH listener is not proof of a completed OAuth flow. Mem describes the supported setup and outstanding account-holder checks.
Next: Security, Maintenance. Documentation home.
Procedures live in the reviewed canonical repository guides. Wiki pages provide navigation and do not add runtime capabilities. Security reporting · Roadmap