Linux – SSL error: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch

linuxopensslsslssl-certificate

ERROR:

SSL error: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch

STEPS:

openssl genrsa -out SITE.TLD.key 2048
openssl req -new -key SITE.TLD.key -out SITE.TLD.csr

(send CSR to SSL site to sign)

add CERT to SITE.TLD.crt
add CA to SITE.TLD.ca

chained them:

cat SITE.TLD.crt SITE.TLD.ca > chained.cert

Any Idea what I am doing wrong? I am using LiteSpeed HTTPd

Best Answer

First check that private key indeed matches by looking at the modulus
diff <(openssl rsa -in KEY -modulus -noout) <(openssl x509 -in CERT -modulus -noout) should produce no output

Related Solutions

Creating a non-MD5 CSR for Verisgn

Just add -sha1 or -sha256 to the end of your request command to specify which message digest algorithm to use. See OpenSSL's Documentation for a list of valid signing algorithms.

For example (SHA-1):

openssl req -new -key server.key -out www.domain.server.csr -sha1

OR (SHA-256):

openssl req -new -key server.key -out www.domain.server.csr -sha256

Ssl – In Stud, which Private RSA Key should be concatenated in the x509 SSL certificate pem file to avoid “self-signed” browser warning

SSL X509 certificate file is a file containing a certificate in the format specified by the ITU in their X series of specifications - specifically x.509. There is no private-key information there as it is a certificate format so things like names, public keys, signatures, validity dates and other goodies go in there - but not private-keys.

PEM is a set of specifications for Privacy Enhanced Mail - it offers for the most part packaging standards that are build off of the PKCS specs (PKCS specs were developed by RSA and RSA labs themselves for public use to enable interoperability between various implementations - this was done again by the IETF and by the community in other arenas). You can use openssl to convert formats around - see here http://www.openssl.org/docs/apps/openssl.html . Concatenation won't help you any.

If the certificate is self-signed then it's kind of odd that a CA gave it to you - that makes me think that you are telling about feeding the Gandi CA certificate to openssl which is telling you that cert is self signed (ergo it is a root or end entity certificate but certainly not an intermediate aka chain certificate).

To address some of your points: 1 Self signed certs will always generate warnings in good clients because they lack trust until the user decides they are trustworthy (or for most users.. until Microsoft , Mozilla Foundation, Google, or Opera) decides the user should trust that CA). If your clients (browsers or whatever) have the CA stored and marked as trusted then this warning won't pop-up. 2 Possibly 3 Looks like you used the right key and CSR with Gandi 4 Looks to me like you need to load the domain key and cert and possibly CA into OpenSSL either via OS level trust configuration or via Stud configuration.

Best Answer

Related Solutions

Creating a non-MD5 CSR for Verisgn

Ssl – In Stud, which Private RSA Key should be concatenated in the x509 SSL certificate pem file to avoid “self-signed” browser warning

Related Topic