Home / server / Questions / 650462
Accepted
Sumit Murari
Asked: 2014-12-10 23:26:27 +0800 CST

After Updating to SHA2, private and public doesn't match

  • 772

I've upgraded to SHA2 certificate, but after upgrading the new certificate key doesn't match my old private key.

Public key has changed after updating and it doesn't match to previous private key.

Is it usual that after upgrading to SHA2, the upgrading public key doesn't match previous SHA1's private key ?

Any pointer's will be helpful ?

public-key

1 Answers

  1. Best Answer

    If the same CSR is used then the new cert would indeed work just fine with the same private key - most likely this was generated with a new key, which you'll need to get from the client.

    Confirm that the new cert was generated with:

    openssl x509 -in path/to/public-cert.pem -noout -text

    Compare the Modulus there to the modulus from:

    openssl rsa -in path/to/private.key -noout -text

    If those don't match, then the new cert did not use the existing private key, and you'll need to get your hands on the new key (or request and issue the cert again with the existing key).

    • 0