Bug #75764 | SSH tunneling ignores the user-specific SSH configuration | ||
---|---|---|---|
Submitted: | 4 Feb 2015 14:37 | Modified: | 19 Mar 2015 5:24 |
Reporter: | Danny Fallon | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.2.4 | OS: | MacOS (10.10.2) |
Assigned to: | CPU Architecture: | Any | |
Tags: | ssh config |
[4 Feb 2015 14:37]
Danny Fallon
[5 Mar 2015 11:27]
Marcin Szalowicz
Thank you for the bug report.
[19 Mar 2015 5:24]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Workbench 6.3.3 release, and here's the changelog entry: The "StrictHostKeyChecking" and "UserKnownHostsFile" variables are now read from the SSH configuration file when using SSH for a MySQL connection. MySQL Workbench will attempt to load this configuration from the following locations: For Windows, "%APPDATA%\MySQL\Workbench\ssh\ssh_config" or "%APPDATA%\MySQL\Workbench\ssh\config". For Linux and OS X, "~/.ssh/ssh_config" or "~/.ssh/config". Thank you for the bug report.