MySQL Bugs: #52236: MySQL Workbench on Windows can't use a "hidden" folder ("dot" folder) w/ssh keys

Bug #52236	MySQL Workbench on Windows can't use a "hidden" folder ("dot" folder) w/ssh keys
Submitted:	19 Mar 2010 21:11	Modified:	25 Mar 2010 12:59
Reporter:	Sheeri Cabral (Candidate Quality Contributor)	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.16	OS:	Windows (XP Pro)
Assigned to:		CPU Architecture:	Any
Tags:	.ssh, hidden folders, qc, windows, workbench

Description:
I have my ssh key (id_dsa) in a "dot" folder (C:\cygwin\home\cabral\.ssh\id_dsa)

When I try to test the connection using "Standard TCP/IP over SSH" with that file, I get:

"Can't connect to MySQL server on '127.0.0.1' (10061)"

A colleague pointed out that it might be because of the .ssh directory, which Windows doesn't always play nicely with.

So I copied C:\cygwin\home\cabral\.ssh\id_dsa to C:\cygwin\home\cabral\foo

I used the same connection that had the error, changed *only* the file to C:\cygwin\home\cabral\foo, and the "Connection parameters are correct".

(For testing, I went back and changed the key file back and got the same error again).

The ssh key is password protected, but that shouldn't factor into things.

How to repeat:
try using an ssh key in a "dot" folder.

Suggested fix:
1) Document this in the web documentation.

2) Change the error so that it's clear the problem is a "dot" folder name.

Hi Sheeri,

what windows version are you running Workbench on? i can't repeat this problem on my win7 x64 box (i always used to keep my key files c:\Users\<myusername>\.ssh )

windows xp pro

Many thanks for writing a bug report. Unfortunately, you are
using an unsupported platform.

http://www.mysql.com/support/supportedplatforms/workbench.html

I was having this exact issue "Can't connect to MySQL server on '127.0.0.1' (10061)" and have also discovered that IT IS because of having a the ssh key in a dot/hidden folder!

You might want to test again with a PASSWORD PROTECTED keyfile to see if that matters, but it is a 100% CONFIRMED BUG on Windows 7 x64 because I have reproduced it on multiple machines using WB 5.2.37 CE Rev. 8576

Please fix this immediately.