Repository navigation
SSHKeeper v0.8.9
This maintenance release makes background SSH port forwarding work with passphrase-protected private keys on Linux and macOS.
Fixed
- Background tunnels with encrypted keys. Profiles configured as
key_passphrasecan now use Start background tunnel and Tunnel + Connect, as well assshkeeper tunnel <alias> --background. An SSH tab no longer needs to stay open for an encrypted-key port forward. - Isolated key handling. SSHKeeper unlocks the configured private key using the existing encrypted vault, loads it into a dedicated per-tunnel
ssh-agent, and starts OpenSSH with a private agent socket. Neither the passphrase nor a decrypted private-key file is left on disk or supplied in process arguments. - Cleanup. Stopping a tunnel also removes its agent and its private socket directory; stale tunnel records clean up the associated resources.
- Unchanged key/agent workflows. Plain keys and existing SSH-agent profiles still start background tunnels without unlocking the vault.
Notes
- The new
key_passphrasebackground mode requires the systemssh-agentexecutable on Linux and macOS. Install OpenSSH client tools if it is missing. - On Windows, use a key already loaded into the Windows SSH agent (
agentprofile) or a foreground tunnel for passphrase-protected keys. - Direct SSH password authentication still requires a foreground tunnel.
- Existing saved port-forward rules and profiles do not need to be changed.
Verification
Automated CI passed on Ubuntu, macOS, and Windows, including cross-builds. A Linux integration test exercises a passphrase-protected Ed25519 key, SSH local forwarding, data transfer, and tunnel shutdown against a local SSH test server. The real customer Portainer endpoint has not been tested in this release process.