>_ sshman

Your SSH keys, in one encrypted vault. Never on disk.

A small command-line SSH key and connection manager. Profiles and private keys live in a single password-encrypted file; connect hands the key to OpenSSH through a private, read-only agent. No daemon, no cloud, no telemetry.

~ bash

  

features

Everything you need to manage SSH access, and nothing that phones home.

AES-256-GCM vault

Key derived with Argon2id (t=3, 64 MiB, p=4). Versioned, fully authenticated header — tampering is detected.

Keys never touch disk

connect loads the key into a per-session, read-only agent used only by your ssh child. Forwarding is always off.

Safe writes

Locked, atomic, fsynced saves with an automatic encrypted backup and one-command restore.

Generate or import

ed25519 by default, RSA 3072/4096 on request. Import existing keys — passphrase-protected ones included.

sendkey & rotation

Install a public key on password-only servers, or rotate keys with --via using the old one.

Script friendly

Tags, favorites, notes, search, --json output with no secrets, explicit exit codes, shell completion.

install

Requires Go 1.26+ to build and the OpenSSH client (ssh) in your PATH.

git clone https://github.com/sshman-org/sshman.git
cd sshman
go build -trimpath -o sshman .

Or grab a prebuilt binary from releases and verify it:

sha256sum -c SHA256SUMS --ignore-missing
gh attestation verify sshman_v*_linux_amd64 --repo sshman-org/sshman

quick start

Four commands from zero to logged in.

sshman init                                   # create the vault (password ≥ 12 chars)
sshman genkey --name web --user deploy --host web.example.com
sshman sendkey --name web                     # ssh asks for the account password once
sshman connect --name web                     # log in with the vault key

commands

Every command accepts --vault PATH.

commandpurpose
initCreate an empty vault
addAdd an entry with an existing key (--key FILE|-)
genkeyGenerate a key pair into a new entry
list / searchBrowse by tag, favorite, key age; --json
show / pubkeyDetails, fingerprint, public key — never the private key
copyCopy ssh user@host -p port to the clipboard
update / rename / deleteEdit entries
connectSSH session (or remote command) with the vault key
sendkeyAppend the public key to remote authorized_keys (--via for rotation)
passwd / restoreChange password, recover from the automatic backup
doctorCheck location, permissions, format and ssh — no password needed
completionbash / zsh completion script

security model

Clear about what it protects — and what it can't.

protects

  • Private keys and host list at rest — one 64 MiB Argon2id run per guess
  • Vault integrity: any modified byte is rejected
  • Refuses symlinked, foreign-owned or world-readable vaults
  • Agent answers only list and sign; never forwarded
  • Your own SSH_AUTH_SOCK agent stays untouched
  • Follows your OpenSSH host-key policy; changed keys always refused

does not protect against

  • Malware running as your user or as root
  • Keyloggers capturing the vault password
  • Old copies of the vault kept by backup / sync tools
  • A weak password chosen despite the policy
⚠ Never lose your vault password. There is no recovery without it.

platforms

Tested in CI on all three.

LinuxmacOSWindows
vault, genkey, sendkey✓✓✓
connect via agent✓ unix socket✓ unix socket✓ named pipe
permission checksmode / owner / symlinkmode / owner / symlinkowner + ACL