MySQL Bugs: #61537: WB 5.2.34 breaks SSH tunnels

Bug #61537	WB 5.2.34 breaks SSH tunnels
Submitted:	16 Jun 2011 14:20	Modified:	30 Aug 2011 20:27
Reporter:	David Beaumont	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.34	OS:	MacOS (10.6.7)
Assigned to:		CPU Architecture:	Any
Tags:	regression, ssh

Description:
5.2.34 breaks connecting to remote servers using SSH tunnels.

How to repeat:
- Open workbench
- Double click on saved connection
- user is presented with error dialog:

Your connection attempt failed for user 'root' from your host to server at 127.0.0.1:3306:
  SSH password input cancelled by user

The user was not presented with the password input dialog for either the SSH tunnel or the MySQL user account.

Suggested fix:
WORKAROUND (not a fix):

- open workbench
- click 'Manage Connections'
- Choose the connection in the pane on the left hand side
- click 'Test Connection'
- Enter the SSH password, followed by the MySQL password, as expected.
- 'Connection parameters are correct.' message is displayed
- Close 'Manage DB Connections' screen
- Double click on the connection as normal and the connection is opened.

A colleague has confirmed to me that he is seeing exactly the same behaviour on Mac OS X 10.6.7 and WB 5.2.34.

Another workaround is to downgrade to 5.2.33

Identical thing happened to me. I upgraded from an older version to the latest 5.2.34, and it broke ALL of my SSH connections. Moreover, the work around did not work around the problem for me. Additionally I've checked some of my server logs /var/log/secure and they show the following (they never had this problem before):

Jul 19 10:09:08 sysop sshd[5180]: error: listen: Address already in use
Jul 19 10:09:08 sysop sshd[5180]: error: channel_setup_fwd_listener: cannot listen to port: 3306

There is clearly a bug in the SSH tunnel support of 5.2.34.

Fixed as of 5.2.35:

+        On Mac OS X, connecting to remote servers using SSH tunnels
+        failed to connect. The workaround was to manually test the
+        connection first, via the <guimenu>Manage Connections</guimenu>
+        menu.