Bug #27669 mysqldump: Got error: 2026: SSL connection error when trying to connect

Submitted:	5 Apr 2007 15:13	Modified:	27 Apr 2007 4:32
Reporter:	Sveta Smirnova	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S3 (Non-critical)
Version:	5.0.38	OS:	Linux
Assigned to:	Magnus Blåudd	CPU Architecture:	Any

Description:
mysqldump from MySQL-client-enterprise-5.0.38-0.rhel4.i386.rpm fails with --ssl option and valid certificates.

How to repeat:
Create certificates as described in manual, start server with ssl support.

Use mysqldump from MySQL-client-enterprise-5.0.38-0.rhel4.i386.rpm:

mysqldump -uroot --ssl-ca=cacert.pem --ssl_cert=client-cert.pem --ssl-key=client-key.pem test t1
mysqldump: Got error: 2026: SSL connection error when trying to connect

mysqldump from 5.0.38 tarballs is not affected

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/24329

ChangeSet@1.2451, 2007-04-11 23:42:53+02:00, msvensson@pilot.blaudden +2 -0
  Bug#27669 mysqldump: Got error: 2026: SSL connection error when trying to connect
   - Add testcase for SSL connection from mysqldump to mysqld

Pushed into 5.0.42

Pushed into 5.1.18-beta

Noted in 5.0.42, 5.1.18 changelogs.

mysqldump could not connect using SSL.

I'm a bit new to this, so maybe I'm missing something, but I only see a test case and test result on the patch patch page, but I don't see any resolution. Granted, I'm not too familiar with the process, but I'm still experriencing this issue on mysql5.0.32 on Debian. Any resolution?

Page generated in 0.042 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.