Bug #88549 TCP/IP over SSH connection method does not work when ProxyCommand is used
Submitted: 20 Nov 2017 6:50 Modified: 12 Feb 2018 8:05
Reporter: Samir Ibradzic (OCA) Email Updates:
Status: Verified Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3.8,6.3.9,6.3.10,8.0.12 OS:Any
Assigned to: CPU Architecture:Any
Tags: ssh paramiko

[20 Nov 2017 6:50] Samir Ibradzic
When ssh client ProxyCommand option is used for connecting to a SSH server, MySQL Workbench will completely ignore it, effectively preventing the connection from being established.

On Liunx, OSX and other unixoids, where OpenSSH client is a standard thing, ProxyCommand is a well supported and used method for bouncing between multiple ssh server hops. This is especially important connection method in complex multiple data-centre environments, where direct ssh connection to a desired serves is often unavailable.

How to repeat:
Attempt to connect to a MySQL server by using a "TCP/IP over SSH" connection method, where "SSH Hostname" is a host matching a "Host" entry in ~/.ssh/config which has a ProxyCommand set. Depending on an network in between the "SSH Hostname" and the client, different error will be thrown, usually a connection timeout.

Suggested fix:
Already have a simple sshtunnel.py patch for this, where can I attach the thing?
[24 Nov 2017 7:08] Samir Ibradzic
make Paramiko do consider ProxyCommand if any

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: myql-workbench-ssh-proxycommand-support.patch (text/x-patch), 1.20 KiB.

[12 Feb 2018 8:05] MySQL Verification Team
Hello Samir,

Thank you for the report and contribution.

[20 Oct 2018 0:27] MySQL Verification Team
https://bugs.mysql.com/bug.php?id=92860 marked as duplicate of this one.