Bug #49307 | Continuous prompts for SSH password | ||
---|---|---|---|
Submitted: | 1 Dec 2009 22:19 | Modified: | 15 Feb 2010 13:54 |
Reporter: | Todd Farmer (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S2 (Serious) |
Version: | 5.2.10 r4680 | OS: | Windows (XP) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[1 Dec 2009 22:19]
Todd Farmer
[3 Dec 2009 15:58]
Mike Lischke
The frequent password query is indeed very annoying, but since it works it would be a P4. However since the password is asked for even if a key file is given, this can be raised to a P3. I wonder, though, if the keyfile really works. It surely does for me and it is quite usual that a client asks for a password if the key was not accepted by the server.
[3 Dec 2009 20:11]
Todd Farmer
I'm not sure exactly what was happening previously, but I entered the path to my key file a few different ways, and got perplexing errors as a result when I test the connection: "Cannot open SSH Tunnel: 56250 INFO Tunnel now open ('127.0.0.1', 3687) -> (10.128.23.135', 22) -> ('127.0.0.1', 3306)" "Cannot open SSH Tunnel: Starting thread..." "Cannot open SSH Tunnel: cmd, args = eval(request, {}, {})" I've tried with forward and backward slashes, with and without quotes, and I continue to get a stream of different errors, including many that suggest that it actually succeeded.
[2 Feb 2010 15:24]
Mike Lischke
Fixed in 5.2
[12 Feb 2010 22:59]
Johannes Taxacher
fixed in repository
[15 Feb 2010 13:54]
Tony Bedford
An entry has been added to the 5.2.16 changelog: When using an SSH connection to manage a remote server, MySQL Workbench repeatedly prompted the user to enter a password, even though a key file had been specified.