Import from ~/.ssh/config
Bring the hosts, keys, jump hosts and environment from your OpenSSH config into a vault.
importssh config~/.ssh/configopensshmigrateproxyjumpinclude
Import from ~/.ssh/config
Already have your servers in an OpenSSH config file? Import them into a vault in one step, with their keys, jump hosts and environment.
How to use it
- Open the vault you want to import into → Hosts.
- Click the + button → Import → From ~/.ssh/config.
- The Import from SSH config drawer lists every named host in the file. Use Filter to narrow the list, and tick the hosts you want.
- Click Import N hosts.
Kubexer reads the same file the ssh command does, including any files it pulls in with Include.
What gets imported
For each Host entry:
- the address (
HostName),PortandUser; - the key file (
IdentityFile), copied into the vault as an identity and encrypted. The same key used by several hosts becomes one identity; - jump hosts from
ProxyJump, as a jump chain; - environment variables from
SetEnv; - the agent from
IdentityAgent, andForwardAgent yes. Hosts that sign through an agent keep using it, and no key is copied. See SSH agent & agent forwarding.
Every imported host gets the ssh-config tag, so you can filter for them.
Each row shows what was found: the key and whether it's readable, the agent, forwards agent, and user@address:port. Notes explain anything that can't be imported as-is.
Good to know
- Only named
Hostentries are imported. Wildcard blocks likeHost *act as defaults for them, as they do inssh. - Hosts already in the vault are left as they are.
- Key files are read on this computer and never pass through the app's window. A passphrase-protected key is marked key · passphrase. It's imported, but add the passphrase to its identity afterwards. Keys shown as key missing or key unreadable can't be copied.
- If the file can't be read, the drawer shows why and offers Try again.