Skip to content

v4.3.2

Latest

Choose a tag to compare

@bvisible bvisible released this 21 Nov 10:43
· 1 commit to main since this release

A fix to the Live page. A command that did not finish, because its call timed
out or its connection dropped, stayed on "running" until the control plane was
restarted (#159, thanks to
@TillNano). It is a display problem only: the commands, their results, the audit
log and approvals were never 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, 4.3.0 and 4.3.1 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.

Fixed

  • A command that did not finish no longer stays "running" on the Live page
    (#159, thanks to @TillNano, who traced it to the line). When an ssh_execute
    call threw instead of returning, a timeout or a dropped connection, the engine
    never told the control plane the command had ended: the entry read "running"
    until the control plane restarted, and the stream's socket stayed open, one of
    each per failed command for as long as the application ran. The engine now
    closes the stream however the call ends, reporting exit -1 (the code the
    reply to the agent already carries) when there is no exit code, and the control
    plane ends an entry itself when its connection closes without an end event, as
    when the engine is killed or its client is closed mid-command. The command, its
    result, the audit log and the approval were never affected.

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