MySQL Bugs: #49090: WB suggests paths with ~ placeholder but is not able to resolve it

Bug #49090	WB suggests paths with ~ placeholder but is not able to resolve it
Submitted:	25 Nov 2009 8:46	Modified:	16 Feb 2010 13:30
Reporter:	Hartmut Holzgraefe	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	workbench 5.2.8	OS:	Linux (Ubuntu 9.10)
Assigned to:		CPU Architecture:	Any

Description:
When creating a new server profile the suggested key file path for a ssh connection is 

  ~/.ssh/id_rsa

Using the default the connection test fails with a "file not found" error though, the users home directory path needs to be given as

  /home/username/.ssh/id_rsa
 
explicitly instead to make it work.

The posix ~ placeholder for "current users home directory" is obviously not resolved.

Same problem in the "new connection" part, there no default is suggested though so it is slightly less of an issue there.

How to repeat:
Try using the suggested ssh key path in "new server profile" ssh setup dialog

Suggested fix:
Replace ~ with current users home directory and ~username with the home directory of the user with name "username" before opening files

Has also previously been reported for the db connection setup as part of bug #47892

This has been fixed previously.

fixed in repository

fixed in repository

An entry has been added to the 5.2.16 changelog:

In the Create a new server instance wizard, using the default SSH Key Path, ~/.ssh/id_rsa, resulted in a 'file not found' error when testing the connection. However, if the path was entered as /home/username/.ssh/id_rsa the connection test was successful. The same problem was also present in the Manage DB Connections dialog.

I've experienced this bug in Remote management section in version 5.2.44, please reopen.