Bug #70995 | MySQL Workbench 6.2 does not recognize pageant | ||
---|---|---|---|
Submitted: | 25 Nov 2013 7:19 | Modified: | 1 Oct 2015 14:37 |
Reporter: | Hidetaka Kimura | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.2.3 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[25 Nov 2013 7:19]
Hidetaka Kimura
[19 Sep 2014 16:42]
Kevin Ernst
This seems to be working for me with 6.1.7 as long as you put the *PuTTY* private key file in the "SSH Key File" field. Strangely, it *continues* to work if you later remove the private key filename from that field, as if it "remembers" to check for a running authentication agent after that. I'll agree that the UI could be more helpful here, and the built-in help documentation doesn't give you *quite* enough to go on.
[29 Sep 2014 13:38]
MySQL Verification Team
Please check version 6.2.3. Thanks.
[1 Oct 2014 0:35]
Hidetaka Kimura
It still does not recognize pageant on 6.2.3. I would like to keep the "SSH Key File" field empty if possible. Here is the log. 09:27:07 [INF][ SSH tunnel]: Starting tunnel 09:27:07 [DB2][ python context]: About to pyrun 'C:\Program Files\MySQL\MySQL Workbench 6.2 CE\sshtunnel.py' 09:27:07 [INF][ SSH tunnel]: Existing SSH tunnel not found, opening new one 09:27:07 [DB1][ mforms managed]: Looking up password for service: ssh@****:22, account: **** 09:27:07 [DB1][ mforms managed]: Loading password cache 09:27:07 [DB1][ mforms managed]: Get special folder 09:27:07 [DB2][ mforms managed]: Decrypting password data 09:27:07 [DB2][ mforms managed]: Filling password cache 09:27:07 [DB1][ mforms managed]: Unloading password cache 09:27:07 [DB1][ mforms backend]: Looking up password for '****'@'ssh@****:22' has failed 09:27:07 [DB1][ mforms backend]: Creating and showing password dialog 09:27:07 [DB1][ mforms managed]: Hiding the wait message 09:27:07 [DB2][ mforms managed]: Wait message was not visibile, nothing to do 09:27:07 [DB2][ mforms managed]: Returning main form 09:27:11 [INF][ SSH tunnel]: Opening SSH tunnel to ****:22 09:27:11 [DB1][ grt]: Thread started 09:27:11 [DB2][sshtunnel.py:do_run:117]: SSH Tunel 1 thread started 09:27:11 [DB2][sshtunnel.py:notify:228]: tunnel_37074: INFO Connecting to SSH server at ****:22... 09:27:11 [DB1][ SSH tunnel]: Waiting on tunnel to connect... 09:27:11 [DB1][sshtunnel.py:wait_connection:446]: INFO: Connecting to SSH server at ****:22... 09:27:11 [DB2][sshtunnel.py:notify:228]: tunnel_37074: ERROR Bad authentication type, the server is not accepting this type of authentication. Allowed ones are: ['publickey'] 09:27:11 [ERR][sshtunnel.py:notify_exception_error:233]: Traceback (most recent call last): File "C:\Program Files\MySQL\MySQL Workbench 6.2 CE\sshtunnel.py", line 265, in _connect_ssh look_for_keys=has_key, allow_agent=has_key) File "C:\Program Files\MySQL\MySQL Workbench 6.2 CE/python/site-packages\paramiko\client.py", line 332, in connect self._auth(username, password, pkey, key_filenames, allow_agent, look_for_keys) File "C:\Program Files\MySQL\MySQL Workbench 6.2 CE/python/site-packages\paramiko\client.py", line 493, in _auth raise saved_exception BadAuthenticationType: Bad authentication type (allowed_types=['publickey'])
[26 Nov 2014 9:11]
Hidetaka Kimura
It still happen on 6.2.
[22 Jul 2015 9:48]
あかさたな あかさたな
I'm still happen on 6.3.4.0.
[1 Sep 2015 14:37]
MySQL Verification Team
Please check for duplicate http://bugs.mysql.com/bug.php?id=76168.
[2 Oct 2015 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".