LP #1660339: Bogus client SSL error messages produced using SSL_get_error not ERR_get_error error code
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Activity
Show:
lpjirasync January 22, 2018 at 2:15 PM
**Comment from Launchpad by: Laurynas Biveinis on: 14-06-2017 08:19:57
See bug 1697700 for X plugin testsuite bits
lpjirasync January 22, 2018 at 2:15 PM
**Comment from Launchpad by: Laurynas Biveinis on: 07-02-2017 04:11:31
https://github.com/percona/percona-server/pull/1361
https://github.com/percona/percona-server/pull/1362
Done
Details
Details
Assignee
Unassigned
UnassignedReporter
lpjirasyncPriority
HighSmart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created January 22, 2018 at 2:15 PM
Updated January 22, 2018 at 2:15 PM
Resolved January 22, 2018 at 2:15 PM
**Reported in Launchpad by Laurynas Biveinis last update 14-06-2017 08:19:58
On 5.6 trunk:
main.ssl-big w4 [ fail ]
Test ended at 2017-01-27 07:57:46
CURRENT_TEST: main.ssl-big
mysqltest: At line 54: query 'connect ssl_con2,localhost,root,,,,,SSL' failed: 2026: SSL connection error: error:00000001:lib(0):func(0):reason(1)
The "error:00000001:lib(0):func(0):reason(1)" part comes from ERR_error_string API, which requires ERR_get_error-returned arg, but is passed SSL_get_error-returned arg instead. The return codes of these two functions have nothing in common, and the resulting error message is bogus.
This is likely the reason for https://bugs.mysql.com/bug.php?id=75311 too.