QuestionQ24

VerifiedAnalyze

A client accessed an HTTPS server at myhost1.example.com by using Chrome. The server provides a certificate with these properties:

  • Subject name: myhost1.example.com
  • SAN: DNS: myhost.example.com
  • Extended Key Usage (EKU): Server authentication
  • Issuer: MyCA_Signing

The server also provides an intermediate CA certificate for MyCA_Signing, signed by MyCA. The client’s Trusted CA Certificate list contains MyCA, but not MyCA_Issuing.

Which factor or factors stop the client from trusting the certificate?

Explanation

The certificate’s DNS SAN is myhost.example.com, not the accessed hostname myhost1.example.com. TLS service identity validation uses the DNS name in the subjectAltName extension; the subject name does not make a mismatching DNS SAN valid. Server authentication is the appropriate EKU, and the supplied MyCA_Signing intermediate chains to the trusted MyCA root, so the absence of MyCA_Issuing does not prevent path validation.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!