Skip to content

Hosts and Connections

Se.Cherkasov edited this page Aug 23, 2026 · 1 revision

Hosts and connections

English · Русский

A host is a saved connection profile. Its identity is a stable id, so renaming it or changing its address keeps history, tunnels and snippet references intact.

Connection types

Type What it is Auth SFTP / forwarding
SSH interactive shell over SSH key, password, certificate, keyboard-interactive yes
Mosh SSH launches mosh-server, then the session runs over Mosh's encrypted UDP same as SSH no
Telnet raw TCP stream with option negotiation (RFC 854) none no
Serial local serial port — desktop native, Android USB-OTG. address is the device (/dev/ttyUSB0, COM3), port is the baud rate none no
Local shell a shell on this machine over a pty, no network none no
Container docker exec / kubectl exec through an SSH host the SSH host's no (they would act on the host, not the container)
VNC remote desktop over RFB optional VNC password, no username —
RDP remote desktop over RDP NLA credentials —

Keep-alive (keepalive@openssh.com, default 30 s) and auto-reconnect apply to SSH and container sessions. Mosh heartbeats itself, so it is never auto-reconnected — that would open a new remote session behind your back.

Authentication

  • Key — a private key from the vault, or a key file on disk that is re-read on every connection (the mode that makes short-lived CA certificates work with tsh login, vault write ssh/sign, step ssh certificate).
  • Password — stored in the vault, or asked at connect time.
  • Certificate — an SSH certificate paired with its key, from the vault or from a file.
  • Keyboard-interactive — the server asks, you answer (2FA code, push confirmation). No stored secret is attempted first.

One credential can serve many hosts; the profile references it by id.

Jump hosts (ProxyJump)

A profile can point at another saved SSH profile as its jump host, and that host can have its own jump — a multi-hop chain. The chain is resolved when you connect: a dangling reference, a non-SSH jump, a jump with no secret, or a cycle fails the connection instead of silently going direct.

Host key trust

First connection to a host shows its fingerprint and asks you to vouch for it (trust on first use). A changed key stops the connection and says what changed. Keys you have accepted live in Vault → Known hosts; a CA you trust to vouch for host keys (@cert-authority) lives beside them and covers every host matching its pattern.

Test connection on the form probes the host without adding its key to known hosts — probing never establishes trust.

Organizing hosts

  • Folders — one group per host, picked from a list (never free text, so Production and production can't become two folders that look like one). The same folder mechanism files snippets, runbooks and keychain secrets.
  • Tags — lowercase labels shown as #chips, used for filtering. The prod tag turns on the production guard and sorts the host first.
  • Notes — a free-form remark per host (maintenance window, owner), shown on hover in the desktop sidebar and in the mobile host details.
  • Search — the sidebar field matches names, tags and addresses.

Importing from ~/.ssh/config

Skerry parses an OpenSSH config and offers its hosts for import. Understood: Host blocks with HostName, Port, User, ProxyJump, IdentityFile, CertificateFile. Wildcard patterns (*, ?) and negations are honoured when matching options, but a pattern never becomes a host of its own. Match blocks and Include are skipped and reported as warnings, so you can see what was not carried over. Imported profiles are ordinary hosts afterwards — nothing keeps reading the file.

Containers

A container profile describes the SSH host that runs the CLI, plus what to exec into: container or pod, namespace, and the shell to start. The host form can list what is running on the host and let you pick.

What connects to what

flowchart LR
  P[Host profile] --> R{connection type}
  R -->|SSH / Mosh / Container| J[Jump chain]
  J --> S[SSH transport]
  S --> SH[Shell channel]
  S --> F[Port forwards]
  S --> FS[SFTP]
  R -->|Telnet / Serial / Local| ST[Stream channel] --> SH
  R -->|VNC / RDP| RD[Remote desktop session]
  SH --> T[Terminal emulator]
Loading

Clone this wiki locally