Bug #61325 | Start Command Line Client doesn't work for connections using SSH | ||
---|---|---|---|
Submitted: | 27 May 2011 12:38 | Modified: | 13 Nov 2012 3:01 |
Reporter: | Daniël van Eeden | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.2.34 | OS: | Linux |
Assigned to: | CPU Architecture: | Any |
[27 May 2011 12:38]
Daniël van Eeden
[31 May 2011 8:40]
Valeriy Kravchuk
On 32-bit Ubuntu 10.04 I entered password for MySQL user, and got command prompt. More clear explanation on what password is needed, as well as using stored password, would be nice features to see though.
[31 May 2011 10:18]
Daniël van Eeden
I don't think D5 is correct. This is not a feature request. Please try to reproduce it like this: 1. Setup a db host 2. Setup a client host 3. Make sure the client can not reach the db host on port 3306. You could do this by binding mysql to 127.0.0.1 or using iptables. 4. Setup WB to use SSH to connect to the database. This should succeed. 5. Try to use the "Start Command Line Client" option and enter the correct password. 6. The connection will not succeed. What likely happend when you tried it was that it used a direct MySQL connection instead of the configured SSH tunnel.
[13 Nov 2012 3:01]
Philip Olson
Fixed as of the upcoming MySQL Workbench 5.2.45, and here's the changelog entry: The "Start Command Line Client" feature would fail to connect with SSH connections. Thank you for the bug report.