Repository navigation
v4.3.1
A security release: upgrade. An ssh_deploy request showed no command on the
approval card, so what it was going to do could not be read
(GHSA-vx67-5jmh-4xq2,
moderate, reported by @Fastyyy123). Every release from 3.0.0 is affected; nothing
else changes (the release pipeline upgrades 3.8.5, 3.8.6, 3.8.7, every 4.0.x,
4.1.0, 4.2.0 and 4.3.0 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.
Security
- The approval card shows what a deploy or an upload is going to do
(GHSA-vx67-5jmh-4xq2, reported by @Fastyyy123). A request without a command line
read "(no command)", so someone approving anssh_deploycould not see its files,
their target paths, or itsrestartoption, which runs as a shell command on the
server as the SSH user (the Deployment Guide has always shown it as one, while the
tool description called it a service). The card now shows the arguments the engine
sent, with every secret already removed, and the tool description and the guide
say whatrestartis.restartitself is unchanged, because existing deployments
pass commands such ascd /opt/app && ./bin/restart;readonlyandrestricted
servers still refusessh_deploy.
Install or update: npm install -g mcp-ssh-manager@4.3.1 (or npm update -g mcp-ssh-manager), or download the desktop application below; the 4.x application updates itself.