Closed Bug 1021039 Opened 11 years ago Closed 11 years ago

Add DigiCert renewed root certificates to NSS

Categories

(NSS :: CA Certificates Code, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
3.16.3

People

(Reporter: kathleen.a.wilson, Unassigned)

References

Details

Attachments

(5 files)

This bug requests inclusion in the NSS root certificate store of the following 5 certificates, owned by DigiCert. Friendly name: DigiCert Assured ID Root G2 Certificate location: http://cacerts.digicert.com/DigiCertAssuredIDRootG2.crt SHA1 Fingerprint: A1:4B:48:D9:43:EE:0A:0E:40:90:4F:3C:E0:A4:C0:91:93:51:5D:3F Trust flags: Websites, Email, Code Signing Test URL: https://assured-id-root-g2.digicert.com/ Friendly name: DigiCert Assured ID Root G3 Certificate location: http://cacerts.digicert.com/DigiCertAssuredIDRootG3.crt SHA1 Fingerprint: F5:17:A2:4F:9A:48:C6:C9:F8:A2:00:26:9F:DC:0F:48:2C:AB:30:89 Trust flags: Websites, Email, Code Signing Test URL: https://assured-id-root-g3.digicert.com/ Friendly name: DigiCert Global Root G2 Certificate location: http://cacerts.digicert.com/DigiCertGlobalRootG2.crt SHA1 Fingerprint: DF:3C:24:F9:BF:D6:66:76:1B:26:80:73:FE:06:D1:CC:8D:4F:82:A4 Trust flags: Websites, Email, Code Signing Test URL: https://global-root-g2.digicert.com/ Friendly name: DigiCert Global Root G3 Certificate location: http://cacerts.digicert.com/DigiCertGlobalRootG3.crt SHA1 Fingerprint: 7E:04:DE:89:6A:3E:66:6D:00:E6:87:D3:3F:FA:D9:3B:E8:3D:34:9E Trust flags: Websites, Email, Code Signing Test URL: https://global-root-g3.digicert.com/ Friendly name: DigiCert Trusted Root G4 Certificate location: http://cacerts.digicert.com/DigiCertTrustedRootG4.crt SHA1 Fingerprint: DD:FB:16:CD:49:31:C9:73:A2:03:7D:3F:C8:3A:4D:7D:77:5D:05:E4 Trust flags: Websites, Email, Code Signing Test URL: https://trusted-root-g4.digicert.com/ This CA has been assessed in accordance with the Mozilla project guidelines, and the certificates approved for inclusion in bug #908827. 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.
Jeremy or Chris, Please see step #1 above.
Blocks: 1021093
The information is correct
Blocks: 1021967
No longer blocks: 1021967
Depends on: 1021967
Flags: needinfo?(jeremy.rowley)
Flags: needinfo?(chris)
Tested and everything appears to function properly. Thanks!
Flags: needinfo?(jeremy.rowley)
Flags: needinfo?(chris)
fixed as part of bug 1021967
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.16.3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: