MySQL Bugs: #57101: Include SSL as a valid connection method

Bug #57101	Include SSL as a valid connection method
Submitted:	29 Sep 2010 12:52	Modified:	10 Nov 2010 16:22
Reporter:	Curt VanCalster	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S4 (Feature request)
Version:	5.2	OS:	Any
Assigned to:	Alfredo Kojima	CPU Architecture:	Any
Tags:	MySQL, SSL, workbench

Description:
The SSL support is not yet complete for mysql workbench. There are a few settings missing (like for the old MySQL Adminstrator: http://dev.mysql.com/doc/administrator/en/mysql-gui-options-ssl-connections.html) before it can be used.

How to repeat:
Click on Manage connections from Workbench.  Select Standard TCP/IP in the connection method and click the advanced tab.  There is a check box for ssl but not able to put in cert info.  

Suggested fix:
Add the ability to have an ssl connection established.

Thank you for the feature request.

As our servers all require SSL, this feature is essential for us. It's command-line only administration until this can be added.

Is there any way to raise the priority of this to a bug? 

The old MySQL Query Browser supported a command-line specified cnf file that could be used to connect via SSL. That this ability is not included in workbench represents a loss of functionality when moving up from legacy tools and is unacceptable.

Beyond this, there is a severe lack of GUI tools that are capable of using SSL alone (no pw; using ssl-ca, ssl-cert, ssl-key). 

The lack of this connection method in Oracle's own software encourages others to ignore it as important and inhibits system administrators ability to have complete freedom in making security/policy decisions, especially where using GUI database tools is critical.

I support raising the priority on this issue. Seeing such essential features being left out from Workbench, it feels like the Query Browser was discontinued way too early.

A modification of my previous statement about discontinuing the Query Browser; it is still a very useful tool. The No Install version worked on my Windows 7 PC without any adjustments. I downloaded it from here:

http://dev.mysql.com/downloads/gui-tools/5.0.html

mysql_rdbms_info.xml

Attachment: mysql_rdbms_info.xml (text/xml), 111.39 KiB.

Options for SSL support have been added to the Advanced Options of TCP/IP connection types.

You can enable SSL support in the currently released version by replacing the mysql_rdbms_info.xml file shipped with WB with the one attached to this bug report. Please report if it works or doesn't for you.

bug #49229 marked as duplicate

I verified the instructions given and it works.  I also used wireshark to verify that the connection is ssl enabled and it was.

Very quick response and completion of this.  Nice Job!

attached xml file worked for me -- thanks very much!

Tested in Windows 7 & Ubuntu Linux & working great. Thanks for the quick response!

Works for me 2 :-)

This is great!  However, please modify your attached XML file and add the SSL properties that were missing to the Standard TCP/IP over SSH as well.  Currently you only added them to the Standard TCP/IP advanced options and they are missing from the "over SSH" advanced options.  I did this locally and it worked for me so a simple copy and paste is all that is needed.

mysql_rdbms_info.xml with SSL support for all connection types

Attachment: mysql_rdbms_info.xml (text/xml), 120.41 KiB.

new options added to  "advanced" tab of connection management dialog.
confirmed in repository

An entry has been added to the 5.2.30 changelog:

If the SSL option was selected for a standard TCP/IP connection, there was no facility provided to enter the SSL certificate details.

I tried to setup this with Mysql Workbench 5.2.30, but it does not work.
Doing a tcpdump on the connection, I noticed the message 'Bad handshake'.
With the Toad client it works.

Any clues? Thanks.