Closed Bug 845132 Opened 9 years ago Closed 9 years ago
Add D-TRUST root certificates to NSS
This bug requests inclusion in the NSS root certificate store of the following certificate, owned by D-TRUST. Friendly name: D-TRUST Root Class 3 CA 2 2009 Certificate location: https://www.d-trust.net/cgi-bin/D-TRUST_Root_Class_3_CA_2_2009.crt SHA1 Fingerprint: 58:E8:AB:B0:36:15:33:FB:80:F7:9B:1B:6D:29:D3:FF:8D:5F:00:F0 Trust flags: Websites Test URL: https://certdemo-ov-valid.ssl.d-trust.net/ Friendly name: D-TRUST Root Class 3 CA 2 EV 2009 Certificate location: https://www.d-trust.net/cgi-bin/D-TRUST_Root_Class_3_CA_2_EV_2009.crt SHA1 Fingerprint: 96:C9:1B:0B:95:B4:10:98:42:FA:D0:D8:22:79:FE:60:FA:B9:16:83 Trust flags: Websites Test URL: https://certdemo-ev-valid.ssl.d-trust.net/ This CA has been assessed in accordance with the Mozilla project guidelines, and the certificates approved for inclusion in bug #467891. 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 certificates, 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 certificates have 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.
Frank, Please see step #1 above.
Kathleen, all of the above information is correct.
Thanks for confirming that the data in this bug is correct. Root inclusions and changes are usually grouped and done as a batch when there is either a large enough set of changes or about every 3 months. At some point in the next 3 months a test build will be provided and this bug will be updated to request that you test it. Since you are cc'd on this bug, you will get notification via email when that happens.
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 the new root certs are included with the correct trust bit set. A representative of the CA needs to also confirm that they have installed the test build and verified that the correct roots are included and the correct trust bit set. https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion
Thanks, looks good also on our side - everything is displayed as it should. One question at this point: we would like to issue organizational / team certificates in near future. Is it possible to enable the trust bit for this already by today in order to make the process of activation faster then?
Adding trust bits requires filing a new bug report and going through the process again. https://wiki.mozilla.org/CA:How_to_apply#Enable_Additional_Trust_Bits_for_an_included_root Generally, updates to already-included root certs are treated with higher priority than adding new CAs to the program.
Whiteboard: test complete
Ok, we will request that later then - thanks, Kathleen!
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.