CA/Application Instructions: Difference between revisions

Jump to navigation Jump to search
Replaced text with current recommendation and Firefox behavior
m (link to examples of CP/CPS reviews)
(Replaced text with current recommendation and Firefox behavior)
Line 337: Line 337:
==== Root certificates with the same subject and different keys ====
==== Root certificates with the same subject and different keys ====


The standards allow for two different CA certs with the same subject and with overlapping validities to have different keys (used for key rollover). The trick is if you pick the wrong CA cert when you are validating your chain, you will fail the signature validation. Because of this, CA's will often put two extensions in their certificates: one called the "Subject Key ID Extension", which is placed in the child, and the other is the "Certificate Authority Key Identifier", placed in the parent. These values are a random value that is unique for each key the CA uses. The child's Subject KeyID must match the parent's Certificate Authority Key Identifier if the latter exists. The standard allows for a way to generate a Auth Key ID from a hash, so it's not strictly necessary to include the Auth Key ID in the parent certificate, but it's good practice. NSS will use Subject Key ID to filter out certificates without the matching Auth Key ID automatically. If the CA issues it's certificates with these extensions, there isn't a problem with 2 certs with the same subject but different keys (or even key length).
The standards allow for two CA certificates to have the same subject names but different subject public keys. Please try to avoid this, because it often leads to confusion and compatibility issues. When verifying an end-entity certificate chaining up to a root certificate with the same subject name as another root certificate, if Firefox is aware of the existence of both root certificates, it will try all possible orderings of (subject, issuer) pairs until it finds the right one. If there are many certificates all with the same subject and issuer names, the number of orderings grows exponentially, so it can take a long time to evaluate the certificate chains. Therefore, it is better to avoid these kinds of situations.
 
Note that for root certificates, Firefox ignores the authority key identifier and subject key identifier extensions.


==== Root certificates with the same subject and same key ====
==== Root certificates with the same subject and same key ====
Confirmed users, Administrators
5,526

edits

Navigation menu