Closed Bug 856678 Opened 9 years ago Closed 9 years ago
.net Certification Authority (2048) root certificate in NSS
This bug requests that the following Entrust root certificate be updated in the NSS root certificate store. Friendly name: Entrust.net Certification Authority (2048) Certificate location: https://bugzilla.mozilla.org/attachment.cgi?id=567058 SHA1 Fingerprint: 50:30:06:09:1D:97:D4:F5:AE:39:F7:CB:E7:92:7D:7D:65:2D:34:31 Trust flags: Websites, Email, Code Signing Test URL: https://2048test.entrust.net This CA has been assessed in accordance with the Mozilla project guidelines, and the certificate approved for inclusion in bug #694536. The next steps are as follows: 1) A representative of the CA must confirm that all the data in this bug is correct, and that the correct certificates have been attached. 2) A Mozilla representative creates a patch with the new certificate, and provides a special test version of Firefox. 3) A representative of the CA uses the test version of Firefox to confirm (by adding a comment in this bug) that the certificate has been correctly imported and that websites work correctly. 4) The Mozilla representative requests that another Mozilla representative review the patch. 5) The Mozilla representative adds (commits) the patch to NSS, then closes this bug as RESOLVED FIXED. 6) At some time after that, various Mozilla products will move to using a version of NSS which contains the certificates. This process is mostly under the control of the release drivers for those products.
Bruce, Please see step #1 above.
(In reply to Kathleen Wilson from comment #1) > Bruce, Please see step #1 above. The data in this bug is correct and the correct certificate is attached.
As part of this bug, I will remove the following old Entrust root: Serial Number: 946059622 (0x3863b966) SHA1 Fingerprint: 80:1D:62:D0:7B:44:9D:5C:5C:03:5C:98:EA:61:FA:44:3C:2A:58:FE Removal of the old root and adding the new root will be done at the same time.
When replacing the old root (lacking basic constraint) with the updated equivalent root (having basic constraint extension): I suggest that we reuse the old "friendly name", for maximum compatibility (for example, if someone used NSS tools to refer to the old root using the friendly name == nickname for identification purposes). The old friendly name was: Entrust.net Premium 2048 Secure Server CA
Yes, I agree with reusing the old "friendly name". Thanks! Kathleen
Please proceed with testing. Important reminder: At this phase, we change the NSS root CA list, which covers domain validation. At this time, please test that your root has been correctly included and that trust flags are set correctly, and that connections to your test site work with basic domain validation status. If you have requested EV (extended validation), this is NOT yet enabled, it will be done at a later time, in a separate bug. The test build is available at http://email@example.com/ Please download a binary for your preferred operating system. (Only if the above link fails, you may use this backup location: https://kuix.de/mozilla/tryserver-roots-20130403/ ) Can a CA representative please verify the trust settings for correctness? FYI: https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion (See also the initial comments in this bug. You should ensure that you're using a fresh profile, to make sure you really see the trust bits provided by this build, not trust settings that you had set manually in an application profile. To learn how to use a separate profile for testing, refer to http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles or http://kb.mozillazine.org/Creating_a_new_Firefox_profile_on_Windows )
I have used the test build and a fresh profile to confirm that the root has been replaced, and that all three trust bits are set. A representative of the CA needs to also confirm that they have installed the test build and verified that the correct root is included and the correct trust bits set. https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion
I have installed the test build provided above and confirmed that the correct CA cert was included and that the trust bits were set appropriately.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.