MySQL Bugs: #74300: After upgrading from MySQL Workbench 6.1.7 to 6.2.3 cannot use key files

Bug #74300	After upgrading from MySQL Workbench 6.1.7 to 6.2.3 cannot use key files
Submitted:	9 Oct 2014 15:15	Modified:	10 Apr 2015 17:20
Reporter:	fred flint	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	6.2.3	OS:	Windows (8.1)
Assigned to:		CPU Architecture:	Any
Tags:	keyfile

Description:
After upgrading MySQL Workbench 64bit from 6.2.2 to 6.2.3 on Windows 8.1 I can no longer use private key files instead of passwords for MySQL connections.  I can still use passwords.

I tried uninstalling and rebooting and installing and rebooting but the problem remains.

How to repeat:
Upgrade from the previous version of Workbench to the current GA GPL version

Correction.

Previous released version was 6.1.7 32bit.  After downgrading back to that key files are working again.

6.2.3 appears to have split into 32bit and 64bit.  Only 64bit would install on Windows 8.1 64bit

update synopsis

Thank you for the report.
I couldn't repeat this issue at my end with latest 6.2.5/6.3.2 builds.
Could you please try with latest build and inform us if you are still having this issue along with workbench log etc to investigate further at our end?

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Yes this still does not work with any 64bit version of Mysql Work bench on any 64bit OS.

Here is the error in the Mysql workbench logfile.

08:08:04 [INF][     SSH tunnel]: TunnelManager.wait_connection authentication error: Authentication error, unhandled exception caught in tunnel manager, please refer to logs for details
08:08:04 [ERR][     SSH tunnel]: Authentication error opening SSH tunnel: Authentication error, unhandled exception caught in tunnel manager, please refer to logs for details
08:08:06 [INF][      WBContext]: Connection to 107.181.232.124 cancelled by user: Tunnel connection cancelled
08:10:49 [INF][     SSH tunnel]: Existing SSH tunnel not found, opening new one
08:10:49 [INF][     SSH tunnel]: Opening SSH tunnel to 107.181.232.124
08:10:49 [ERR][sshtunnel.py:notify_exception_error:233]: Traceback (most recent call last):
  File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\sshtunnel.py", line 297, in _connect_ssh
    look_for_keys=has_key, allow_agent=has_key)
  File "C:\Program Files\MySQL\MySQL Workbench 6.3 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.3 CE/python/site-packages\paramiko\client.py", line 445, in _auth
    self._agent = Agent()
  File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE/python/site-packages\paramiko\agent.py", line 78, in __init__
    ptype, result = self._send_message(chr(SSH2_AGENTC_REQUEST_IDENTITIES))
  File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE/python/site-packages\paramiko\agent.py", line 110, in _send_message
    l = self._read_all(4)
  File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE/python/site-packages\paramiko\agent.py", line 118, in _read_all
    raise SSHException('lost ssh-agent')
SSHException: lost ssh-agent

See this bug report from someone else describing exactly the same thing.

https://bugs.mysql.com/bug.php?id=76168