Bug #76508 SSL and named pipes failure
Submitted: 27 Mar 2015 14:14 Modified: 21 May 2015 14:06
Reporter: Todd Farmer (OCA) Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:5.7.6 OS:Any
Assigned to: CPU Architecture:Any

[27 Mar 2015 14:14] Todd Farmer
SSL doesn't work with non-TCP connections - at least some of them, such as Windows Named Pipe.  After WL#7712, libmysqlclient's preference for SSL affects such protocols, resulting in an (ugly) error unless --skip-ssl is also used:

R:\ade\mysql-5.8.0-m17-winx64>bin\mysql.exe -uroot --protocol=pipe
ERROR 2026 (HY000): SSL connection error:
error:00000005:lib(0):func(0):DH lib

R:\ade\mysql-5.8.0-m17-winx64>bin\mysql.exe -uroot --protocol=pipe --skip-ssl
Welcome to the MySQL monitor.  Commands end with ; or \g.

How to repeat:
* Start MySQL 5.7.6+ with named pipes enabled on Windows
* Try to connect using --protocol=pipe
* Observe error message

Suggested fix:
Enable SSL with named pipes.
Check shared memory connections with/without SSL.
[21 May 2015 14:06] Paul DuBois
Noted in 5.7.8, 5.8.0 changelogs.

SSL did not work for named-pipe connections.
[31 May 2015 22:42] Paul DuBois
Revised changelog entry:

Attempts to use SSL for named pipe and shared memory connections now
produce an error because SSL does not add anything for these
connection protcols.