[CONC-639] Unable to connect to SSL using client certificates SEC_E_ALGORITHM_MISMATCH Created: 2023-03-12 Updated: 2023-11-12 |
|
| Status: | Stalled |
| Project: | MariaDB Connector/C |
| Component/s: | TLS/SSL |
| Affects Version/s: | None |
| Fix Version/s: | 3.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Lotendan | Assignee: | Georg Richter |
| Resolution: | Unresolved | Votes: | 6 |
| Labels: | None | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Description |
|
Hello, I have set up a secure SSL connection between a Mariadb client and a Mariadb server. I use HeidiSQL client (compiled with MariaDB Connector C). When upgrading the server from OpenSSL 2.x to the latest version of OpenSSL 3.x, the client will refuse to connect and closes the connection with error: SEC_E_ALGORITHM_MISMATCH. The logs of the server are not helpful either. The server only sees an aborted connection from the client.
I initially submitted a ticket to HeidiSQL team, but the problem was not related: I have submitted an issue to OpenSSL as well and explained the problems in great details here: Please find attached the Wireshark capture (same as Openssl GitHub issue above #20138) Note: this is probably a duplicate from: Thanks a lot, best regards |
| Comments |
| Comment by Lotendan [ 2023-05-28 ] |
|
Hello, any news on this issue please? |
| Comment by Georg Richter [ 2023-06-23 ] |
|
A possible reason might be the deprecation of SCHANNEL_CRED structure, which was deprecated since Windows 10 1809 and needs to be replaced by SCH_CREDENTIALS I filed a new task CONC-653 (TLSv1.3 support in Schannel) which will hopefully also solve this issue. |
| Comment by Yoh [ 2023-11-12 ] |
|
Hi, |