Every key, at a glance
Each key in ~/.ssh gets a card with its type, fingerprint, comment, file names and passphrase status. The public key is one click from your clipboard, or share it with the system share sheet.
Native macOS · SwiftUI · 100% OpenSSH-compatible
EasySSHConfig shows every key in ~/.ssh, creates new ones in seconds, and lets you drag any host onto the key it should use. It writes plain ssh_config, so it keeps working even if you delete the app.
Your browser can't show WebGL, so the live Config Matrix is hidden.
The same Three.js module that runs inside the app: your ~/.ssh/config as a glyph wall with a live hex dump. Keys are hexagons and hosts are diamonds. Dashed lines come from your own config, and missing keys glitch red. These are sample keys.
// what it does
Each key in ~/.ssh gets a card with its type, fingerprint, comment, file names and passphrase status. The public key is one click from your clipboard, or share it with the system share sheet.
Ed25519 by default, with RSA 3072/4096 and ECDSA available. Add an optional passphrase and choose to remember it in your Keychain. You can assign hosts and copy the public key from the same sheet.
Every address sits in one list. Drag it onto a key, or drop a URL straight from your browser. Wildcards like *.corp.example.com and web-?? work, and undo is ⌘Z.
git.corp.example.com overrides *.corp.example.com, which overrides *. The app writes the exclusions for you, so each host gets exactly one key and no surprise fallbacks.
Type a host and see what ssh will really do: which key, which rule matched, and the hostname, port and user it connects to. The answer comes from ssh -G, not a guess.
The app owns one file. It adds a single Include line to yours, backs it up first, has ssh check every change, and rolls back if ssh objects.
It flags keys that ssh refuses to use because others can read them, missing or mismatched .pub files, weak keys and duplicates. It also catches key files your config names that don't exist, and hosts that get offered extra keys.
Personal and work GitHub? Create an alias like github.com-work that uses a different key, then git clone git@github.com-work:org/repo.git.
Your existing Host blocks show up next to their keys. Import one to manage it in the app: only its IdentityFile lines move, and everything else in the block stays exactly as you wrote it.
// try it right here
This is a working replica of the app. Drag the host chips between keys, or use the dropdowns on the right. The preview recompiles with the same rules the app uses. Nothing leaves your browser.
~/.ssh/☑ Valid OpenSSH syntax
// how it decides
Normally ssh adds up every IdentityFile that matches a host and offers the keys one after another. EasySSHConfig checks rules from most to least specific, so the first match is the only key ssh sees.
Your browser can't show WebGL. The trace on the right still works.
// paste anything
Paste a git remote, a browser URL, an ssh:// link with a port, or an IPv6 address. EasySSHConfig keeps only what ssh matches on, which is the host. It never captures a user name, and it explains when something can't work, such as CIDR ranges.
// safe by construction
EasySSHConfig touches ~/.ssh/config in exactly two narrow ways, and only after asking you. Everything else goes into one file of its own.
+ # Added by EasySSHConfig.app — keep this first. + Include ~/.ssh/easysshconfig-managed.conf # your own config, untouched Host legacy.example.com User deploy ProxyJump bastion.example.com
ssh -G reads the whole config, exactly as a real connection would.// get the app
For macOS 14 Sonoma and later, on Apple silicon and Intel. A notarized download is coming soon.
Native SwiftUI. No account needed. Nothing phones home.
// questions
~/.ssh/config?No. Read-only browsing never writes anything. The first time you assign an address, the app shows exactly the two lines it will add and where the backup goes. After that it only rewrites its own file. Importing one of your rules removes only that rule's IdentityFile and IdentitiesOnly lines, after showing you a preview.
Yes. A .pub file without its private key shows up as an "Agent-backed" key, and you can assign hosts to it like any other. ssh then asks your agent for the private half.
Your keys and config are ordinary OpenSSH files. Delete the two lines it added (or use Settings ▸ Turn Off App-Managed Rules) and ssh behaves exactly as before.
ssh tries every key that matches, in order. Servers can lock you out after too many failed attempts, or you can end up signed in as the wrong account. One key per host avoids both.
Yes. Assign github.com to your personal key, then create an alias such as github.com-work for your work key. Clone work repos with git@github.com-work:org/repo.git.
Not at launch. Managing ~/.ssh and running Apple's own ssh-keygen doesn't fit the App Store sandbox, so it will be a signed, notarized direct download instead.