Yet another SSL-does-not-work-with-MySQL user...
I'm having the same issues others have getting SSL to work with MySQL and it's very disturbing. I've attempted to make it work with MySQL 5.0.27 and 5.0.51 using OpenSSL 0.9.8d and 0.9.8g. The error returned is ERROR 2026 (HY000): SSL connection error.
I've tried this on three different servers. I've tried connecting locally using SSL and remotely using SSL. I've opened up my firewall completely in some cases to test.
I have tried so many things to try to get it to work that I'm almost literally pulling my hair out.
I've created my own CA certificate used to create and sign server/client keys and certificates. I've made the common names unique for each of the certificates. I've verified that these work by integrating them into Apache. I've put them in a 'mysql' owned directory with 700 permissions, files with 600 permissions (thinking OpenSSL wouldn't like it any other way). I've tried changing ownership of those files to root. I've verified that 'have_ssl' and 'have_openssl' switch from DISABLED to YES once I enable ssl-ca, ssl-key, and ssl-cert in my.cnf. I've tried adding ssl=1 to my.cnf. I've tried running mysqld with the --ssl switch. My ssl variables (i.e., show variables) all match to the files I specified. I've added a connect-timeout variable in my.cnf and set it to 60 seconds.
I've even sniffed the packets both ways during the attempted connection. The only thing I've seen in the packets that hasn't been mentioned anywhere else on the web is the server responds to the client with a '#8S01 Bad handshake' message.
Good grief! What's wrong? Please help! There is very little information about this on the web. I'm starting to think that OpenSSL and MySQL just DO NOT work together. Please someone tell me this isn't true because I NEED it to work.
Subject
Views
Written By
Posted
Yet another SSL-does-not-work-with-MySQL user...
7471
March 20, 2008 11:03AM
4098
March 24, 2008 04:29PM
4567
April 03, 2008 03:19PM
Sorry, you can't reply to this topic. It has been closed.
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.