Closed Bug 856695 Opened 9 years ago Closed 9 years ago
Add renewed Swisscom root certificates to NSS
This bug requests inclusion in the NSS root certificate store of the following certificates, owned by Swisscom. Friendly name: Swisscom Root CA 2 Certificate location: http://aia.swissdigicert.ch/sdcs-root2.crt SHA1 Fingerprint: 77:47:4F:C6:30:E4:0F:4C:47:64:3F:84:BA:B8:C6:95:4A:8A:41:EC Trust flags: Websites, Email, Code Signing Test URL:https://test-emerald-ca-2.pre.swissdigicert.ch/ Friendly name: Swisscom Root EV CA 2 Certificate location: http://www.swissdigicert.ch/download/sdcs-root2-ev.crt SHA1 Fingerprint: E7:A1:90:29:D3:D5:52:DC:0D:0F:C6:92:D3:EA:88:0D:15:2E:1A:6B Trust flags: Websites, Code Signing Test URL: https://test-quarz-ev-ca-2.pre.swissdigicert.ch/ This CA has been assessed in accordance with the Mozilla project guidelines, and the certificates approved for inclusion in bug #759732. 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.
Patrick, Please see step #1 above.
The information is correct and the correct certificates have been attached.
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 bits 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 bits set. https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion
I have also used the test build with a fresh profile to confirm the new root certificats are included as builtin object tokens with the correct trust bits set.
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.