Secure Shell (SSH) connections rely on a plain-text configuration file that maps host aliases to connection parameters, letting you reach remote servers with short, memorable commands. Manually maintaining the file becomes difficult as projects grow, directives vary, and wildcard mappings appear, causing connection errors, duplicated keys, and lost productivity for busy administrators.
This browser-based editor parses your existing file, categorises entries, and presents every directive in a dynamic form. A lightweight dynamic engine updates changes instantly, while grouping controls reveal wildcard, domain, or ungrouped views. Because all processing stays client-side, your sensitive hostnames, usernames, and key paths never leave the machine, safeguarding privacy.
Use this editor whenever you adopt fresh cloud instances, rotate aged keys, or merge legacy environment files; its instant validation ensures consistent directives, clean indentation, and predictable grouping, while offline export integrates neatly into commit workflows—always generate a secure backup before replacing production-critical files to prevent unexpected lockouts and recovery downtime.
Technical Details:
The tool runs entirely in the browser, parsing text via a lightweight JavaScript engine and rendering a dynamic form bound to each directive. Grouping logic filters hosts by wildcard symbols or top-level domains, and a Blob exporter writes a fresh file without server interaction. Accessibility semantics and Bootstrap utilities ensure consistent behaviour across devices.
Robust Parsing
The parser recognises comments, whitespace, and unknown directives, preserving order while normalising spacing for readability.
Instant Grouping
Select wildcard or domain grouping to reveal structural patterns and spot redundant entries quickly.
Inline Editing
Edit host patterns and directives in place; changes re-render immediately with no page reload.
Custom Directive Support
Add non-standard keys through a flexible “Custom” option, ensuring compatibility with bespoke environments.
Offline Export
Generate a clean configuration file client-side using Blob downloads, eliminating any need for server storage.
Step-by-Step Guide:
Follow these steps to transform and download a refined SSH configuration.
- Click Select SSH Config File and choose your existing
config
file. - Use the Group Hosts By dropdown to switch between Wildcard, Domain, or no grouping views.
- Expand a host accordion and adjust Host Pattern or directive values as required.
- Press Add Host to introduce a new entry, or remove outdated items with the Remove Host button.
- When satisfied, click Download Updated Config to save the revised file locally.
- Replace your original
~/.ssh/config
with the downloaded file and test connections.
FAQ:
Find quick answers to common questions.
Is my data stored?
No. All parsing and editing occur locally; the application never uploads or logs your configuration.
What file formats are supported?
You can load any plain-text SSH configuration, including .conf
and .txt
extensions.
Can I edit multiple hosts at once?
Yes. Expand each host accordion, make changes, then download a single consolidated file.
Do wildcard entries stay intact?
The editor preserves wildcard patterns and allows you to group or re-label them for clarity.
Will comments be removed?
Existing comments remain untouched; new directives are added beneath original comment blocks.
Troubleshooting:
Resolve typical issues quickly.
- Downloaded file appears empty — ensure at least one host entry remains before exporting.
- Grouping shows no effect — verify the Group Hosts By dropdown is not set to
none
. - Removed directives reappear — confirm you clicked Download Updated Config after edits.
- Unicode characters break the file — stick to UTF-8 encoding when editing custom keys.
- SSH rejects new config — restore backup and validate syntax with
ssh -G host
for diagnostics.
Advanced Tips:
Enhance your workflow with expert advice.
- Prefix host patterns with project codes to filter quickly using terminal auto-completion.
- Store identity files per project folder and reference them with relative paths for portability.
- Set
ControlPersist
to reduce repeated authentication overhead when running scripted tasks. - Use wildcard patterns to consolidate staging or testing hosts under a single block.
- Commit the generated config to version control for auditability and rollback.
Glossary:
Key terms used throughout this tool.
- Host Pattern
- A matching expression telling SSH which servers a block applies to.
- Directive
- A key–value pair that modifies connection behaviour.
- Wildcard
- A character, usually
*
, representing any sequence of characters. - Blob
- Binary large object used here to generate downloadable files client-side.
- IdentityFile
- Path to the private key used for authenticating SSH connections.