Tag Info

New answers tagged

1

It turns out that Thawte's site is just confusing for people who don't work with SSL certs a lot. Despite the fact that there are two certificates shown for SSL123 SHA2 under SHA-1 Root, you only need the first one. The second certificate is the SHA-1 root, and you don't need it concatenated with your site's cert for deployment to nginx. Just use the first ...


3

Your own certificate is signed by exactly one certificate. This means that your certificate is at one end of exactly one of these Thawte chains, you would need a different certificate to be in the other chain (one signed by the intermediate certificate from that chain). As for the signature of the root certificate being SHA-1, SHA-2 or something else it is ...


0

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 ...



Top 50 recent answers are included