Revision history [back]

Wireshark uses libssh for the ssh connection so behavior will depend on that code.
Recently the Wireshark sshlib libraries have been updated for macos and windows.

Here is behavior on Windows for libssh-0.7.3 (Wireshark 3.4.x and earlier):



The connection failed - server was locked down to not support old kex algorithms.

Here is a conenction to the same server with development branch (3.5.0rc0-355-g4227e5a1adef) which uses libssh-0.9.5:

Wireshark uses libssh for the ssh connection so behavior will depend on that code.
Recently the Wireshark sshlib libraries have been updated for macos and windows.

Here is behavior on Windows for libssh-0.7.3 (Wireshark 3.4.x and earlier):



The connection failed - server was locked down to not support old kex algorithms.

Here is a conenction connection to the same server with development branch (3.5.0rc0-355-g4227e5a1adef) which uses libssh-0.9.5:

Wireshark uses libssh for the ssh connection so behavior will depend on that code.
Recently the Wireshark sshlib libraries have been updated for macos and windows.
Looking through the (libssh) code, there were changes in how this was handled between versions.

Here is behavior on Windows for libssh-0.7.3 (Wireshark 3.4.x and earlier):



The connection failed - server was locked down to not support old kex algorithms.

Here is a connection to the same server with development branch (3.5.0rc0-355-g4227e5a1adef) which uses libssh-0.9.5:

Wireshark uses libssh for the ssh connection so behavior will depend on that code.
Recently the Wireshark sshlib ssh libraries have been updated for macos and windows.
Looking through the (libssh) code, there were changes in how this was handled between versions.

Here is behavior on Windows for libssh-0.7.3 (Wireshark 3.4.x and earlier):



The connection failed - server was locked down to not support old kex algorithms.

Here is a connection to the same server with development branch (3.5.0rc0-355-g4227e5a1adef) which uses libssh-0.9.5: