This question already has an answer here:

I came across a certificate that has a signer that is SHA1 but it is a SHA2 certificate. Is this actually allowed or is did the CA screw up ? Would it work with a TLS 1.2 negotiation?

marked as duplicate by gowenfawr, Steve, CaffeineAddiction, Steffen Ullrich tls Mar 11 '17 at 8:14

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 1
    Is the SHA1 the root or an intermediate? Note that the SHA1 problem does not impact trusted root certs because, by definition, they're trusted; their authority derives from you having them and not from being checked against their signature. – gowenfawr Mar 9 '17 at 21:59
  • It is the root certificate that has it. So that has answered my question. Thanks!!! – Thomas Cosenza Mar 9 '17 at 23:39

Browse other questions tagged or ask your own question.