You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to MRSP section 5.3, Intermediate CA certificates created after January 1, 2019, MUST NOT include both the id-kp-serverAuth and id-kp-emailProtection KeyPurposeIds in the same certificate. However, the MRSP is silent on whether the same principle should be applied to root certificates. A question has been raised regarding when Mozilla might require the submission of TLS-specific or S/MIME-specific root CA certificates for inclusion. If such a requirement is planned, we need clarification on what the policy will be and the timeline for its implementation
The text was updated successfully, but these errors were encountered:
According to MRSP section 5.3, Intermediate CA certificates created after January 1, 2019, MUST NOT include both the id-kp-serverAuth and id-kp-emailProtection KeyPurposeIds in the same certificate. However, the MRSP is silent on whether the same principle should be applied to root certificates. A question has been raised regarding when Mozilla might require the submission of TLS-specific or S/MIME-specific root CA certificates for inclusion. If such a requirement is planned, we need clarification on what the policy will be and the timeline for its implementation
The text was updated successfully, but these errors were encountered: