SSH server deployment¶
Build a bundle for the destination computer before using gft remote connect.
For user setup, see remote access.
Build a bundle¶
- Build on the destination platform, or a matching VM/CI runner.
- Output:
dist/remote/<os>-<arch>/. - Copy that folder into the client's
dist/remote/. - The CLI selects the matching OS/CPU bundle; it does not download a substitute.
Or provide an executable built for the destination:
Install the bundle¶
- Linux/macOS: binaries under
~/.local/lib/graffitty/; descriptor and log under~/.local/state/graffitty/. - Windows OpenSSH: bundles under
%LOCALAPPDATA%\graffitty\bin; descriptor under%LOCALAPPDATA%\graffitty\state. - Connections use normal OpenSSH authentication and host-key checking.
- Existing daemons are reused; uploading a bundle does not replace a running daemon.
- Plan upgrades separately from connecting. Do not kill a server with live sessions just to deploy a bundle.
- Hosts that terminate user processes on logout need a service/session policy allowing persistence.
Keep a tunnel without opening a GUI¶
Complete any required Telegram code through a GUI connection first.
- Keep the command running.
- Open its printed connection file with
gft-gui -- --remote-connections=PATH. - Ctrl+C closes the tunnel without stopping the remote server.
- Treat temporary connection files as secrets.
Headless authentication¶
These commands save settings and exit; they do not start a listener:
gft server --set-password
gft server --temporary-password-length 8
gft server --telegram-credential graffitty-2fa --telegram-chat-id 123
gft server --telegram-credential off
gft server --clear-password
--set-passworduses a hidden local prompt.--clear-passwordreturns to temporary passwords.- Use
--auth-file PATHfor independent server credentials. - Restart an already-running server to apply changes.
- Authentication state stores a password verifier, not the password. See encryption and its limits for transport protection.