Bug #68787 MySQL Workbench SE fails to connect to MySQL Server 5.6.10 using SSL

Submitted: 26 Mar 2013 21:34 Modified: 15 Apr 2014 13:26
Reporter: Jonathan Weaver Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.46 OS:Windows
Assigned to: CPU Architecture:Any

[26 Mar 2013 21:34] Jonathan Weaver
Description:
MySQL Workbench SE fails to connect to MySQL Server 5.6.10 using SSL with the following error message...

ERROR 2026 (HY000): SSL connection error: unknown error number

According to the documentation, Workbench version 5.2.46 and greater is supposed to include the 5.6.10 clients.  However, running "mysql.exe --version" reports version 5.5.16 for Workbench versions 5.2.46 and 5.2.47.

Regardless of the CLI utility version, I assume that the Python connector needs to be updated to support MySQL Enterprise version 5.6.

How to repeat:
Create a workbench connection to a MySQL Enterprise 5.6.10 server with SSL support configured.  In the advanced tab at a minimum, specify the CA certificate file location.  After the connection is created, attempt to make a connection to the server.  The following error will be returned...

SSL connection error: unknown error number
[24 Apr 2013 14:00] MySQL Verification Team
Hello Jonathan,

Thank you for the bug report, duplicate of http://bugs.mysql.com/bug.php?id=68788 

Regards,
Umesh
[2 Aug 2013 18:24] Jonathan Weaver
I downloaded MySQL Workbench 6.0.4 CE and I receive the same error when connecting to MySQL Enterprise 5.6.12 over SSL.  Is there any update on this issue?

Thank you,
[15 Apr 2014 12:19] Arnaud Adant
Workbench 6.1.4 is still hit by this bug. Reopening.
[15 Apr 2014 13:26] Arnaud Adant
Duplicate of an internal bug : Bug 18070573 - BUILD WORKBENCH WITH FIX TO BUG 16715064 

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.