Repository navigation
A security release: upgrade if you use restricted mode. On a server in
restricted mode, a command could be hidden from the allowlist and still run
(GHSA-86xm-rv3h-r4f2,
high, reported by @Fastyyy123). Every release from 3.8.6 is affected. Servers in
readonly mode and servers without a mode are not (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, 4.3.0,
4.3.1 and 4.3.2 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
restrictedmode no longer lets a command hide from the allowlist
(GHSA-86xm-rv3h-r4f2, reported by @Fastyyy123). The allowlist is checked against
each command the line runs, found by reading the line, and the reader did not
recognise comments: a quote or a trailing backslash in one made it see fewer
commands than the shell ran, soecho x # it'sfollowed by a line withtouch
and a second apostrophe rantouchon a server that allowed only^echo. Looking
for the same thing in other places found four more ways, fixed together: a
here-document body that opens a quote; an ANSI-C quote ($'a\'b', which ends
at a different place in dash than in bash, ksh and zsh); a${…}that is more than
a plain name, which includes${ command; }of ksh and bash 5.3; and parentheses,
which zsh and fish read as commands (echo =(touch x)), reachable when the login
shell reads the line, that is withtimeout: 300000or in a session. Comments are
now read as comments and left out of the command they follow (so an apostrophe or
a;in a comment is no longer a refusal), and the other four are refused with a
reason. Unquoted parentheses, here-documents,$'…'and${x:-word}in a command
thatrestrictedmode allows were never reliable, and are now refused.readonly
mode is not affected: it also tests the whole line. A new test runs random lines
through the policy and the shells of the machine (sh, dash, bash, zsh) and fails if
one the policy allows runs a command it never checked.
Install or update: npm install -g mcp-ssh-manager@4.3.3 (or npm update -g mcp-ssh-manager), or download the desktop application below; the 4.x application updates itself.