Generate SSH client config files (~/.ssh/config) with host entries, jump proxies, and key specifications.
The tool turns each server you connect to - alias, hostname, user, port, key file, and any jump host - into a ready-to-paste block of ssh_config text for ~/.ssh/config, so you fill in fields instead of remembering keyword syntax. The format is pickier than it looks: keywords are case-insensitive and indentation is conventional, but the matching rules are exact. The thing people get wrong most often is ordering: ssh reads the file top to bottom and keeps the first value it finds for each option, so a broad Host * defaults block placed before your entries silently overrides them. Specific hosts first, defaults last.
A concrete input and expected output from the current implementation.
Input
Fields: Alias web-prod; Hostname 203.0.113.42; User deploy; Port 2202; Key file ~/.ssh/web-prod; Jump host [email protected]
Expected output
Host web-prod
HostName 203.0.113.42
User deploy
Port 2202
IdentityFile ~/.ssh/web-prod
ProxyJump [email protected] Each field maps to one ssh_config keyword, so ssh web-prod now connects as deploy to 203.0.113.42 on port 2202 with the named key, routed through the bastion on its default port 22. The tilde in the IdentityFile stays literal in the file; ssh expands it when the connection runs.
Each entry becomes one Host block: the alias you enter is written after the Host keyword, and everything below it applies to connections matching that name. ssh scans the whole config top to bottom and applies the first value it finds for each option, so a later block only supplies options an earlier one left unset. Generated entries therefore behave predictably when placed before any catch-all defaults.
A key file becomes an IdentityFile line and a jump host becomes ProxyJump. Each hop authenticates independently: the bastion leg uses the user and keys named in the jump spec, the target leg uses the block's own User and IdentityFile. ProxyJump requires OpenSSH 7.3 or newer, covering any client from 2016 on. The text and your key paths stay in the browser; the output is plain text to save.
Save it as ~/.ssh/config, or append the block to that file if it already has content. ssh reads the file on every connection, so changes take effect immediately, with no restart or reload. Keep the file at permissions 600, since ssh ignores configs that are group- or world-writable. To keep generated entries separate, save them to another file and connect with ssh -F /path/to/config alias.
By default, ssh offers keys loaded in your ssh-agent alongside the IdentityFile you listed, and the server chooses what it accepts, so your file is not the only key in play. Add IdentitiesOnly yes to the block and ssh will offer only the listed key files. If it still fails, check that the key path exists and the key's permissions are 600.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.