Skip to content

v4.1.0

Choose a tag to compare

@bvisible bvisible released this 13 Nov 12:02
· 29 commits to main since this release

Choose the agent key per server, and sudo in the audit log. Nothing to
change on upgrade: the new option is off unless you set it, and the audit log
only gains lines when AUDIT_LOG is already on (the release pipeline upgrades
3.8.5, 3.8.6, 3.8.7 and every 4.0.x from the registry to this version and back).

The Windows installer is still not Authenticode-signed, for the same reason
as 4.0.0: Windows shows "Windows protected your PC", More info → Run anyway,
and ssh-manager app checks the installer against the SHA-256 in
release-manifest-win32.json. macOS builds are signed and notarized.

Added

  • Pick which key of the SSH agent a server uses (#128, thanks to
    @RebornOnce). When the agent holds many keys (a password manager's agent,
    say), a server can hit MaxAuthTries and close the connection before the
    right one is offered. agent_public_key_path in TOML, or
    SSH_SERVER_<NAME>_AGENT_PUBLIC_KEY_PATH in .env, names a public key file:
    only that identity is offered and used for signing, and the private key never
    leaves the agent. If the agent does not hold it, the connection fails instead
    of trying the others. It cannot be combined with a key, a password, a
    certificate or agent forwarding, and nothing changes for servers without it.
    ssh_sync uses the system's ssh, which takes IdentityFile and
    IdentitiesOnly yes from your SSH configuration instead.
  • llms-install.md: the steps an agent follows to set the server up for its
    user (Node, the client entry, servers described in ~/.ssh-manager/.env with
    a key and never a password typed into the conversation, then a check). It is
    what the Cline MCP Marketplace asks for, and any agent can follow it.

Fixed

  • The audit log records what sudo commands did (#133, reported by
    @revert12; #134, thanks to @orshih6). With AUDIT_LOG set, only
    ssh_execute and ssh_upload wrote their outcome: a command run through
    ssh_execute_sudo that the policy allowed left no line at all. It now records
    the exit code and success (the logged arguments are the command and the
    working directory, never the password), and so do ssh_download,
    ssh_execute_group (one line per server) and commands sent to a persistent
    session (success only: sessions report no exit code). Other tools still record
    only a denial or an approval decision.

Security

  • The desktop build uses a fixed minimatch. electron-builder, the tool
    that builds the desktop app, pulled minimatch 10.2.6 and 9.0.9, open to a
    denial of service through crafted glob patterns (GHSA-g3hv-75wg-m249). Nothing
    was exposed: the tool only reads the patterns of our own build configuration,
    and no copy of minimatch ships in the app or in the npm package. An npm
    overrides entry in desktop/electron/package.json now resolves those copies
    to 11.x; a build with it contains the same files as one without, the
    package.json line aside. Remove the entry once app-builder-lib itself
    requires minimatch 11.0.1 or later.

  • @hono/node-server 2.1.8 and hono 4.13.18 in the lockfile. Two
    moderate advisories for the first (GHSA-qv5m-9pm6-hqp3, GHSA-jpvv-r467-5p4w),
    five for the second (four moderate, one low: GHSA-46wx-v44x-9hh2,
    GHSA-4h7h-rv7c-7m2v, GHSA-4m76-xfj5-7975, GHSA-h7mg-cq63-vhpq,
    GHSA-3gg2-335m-rxc6). The MCP SDK pulls both for its HTTP transport; the
    stdio server this package runs never imports them, so nothing was exposed.


Install or update: npm install -g mcp-ssh-manager@4.1.0 (or npm update -g mcp-ssh-manager), or download the desktop application below; the 4.0.x application updates itself.