This bug requests the following changes to the NSS root certificate store, to remove an old root cert and turn off trust bits that are not being used for other root certs. As per Bug #841968, remove the following root cert: Friendly Name: Equifax Secure eBusiness CA 2 OU = Equifax Secure eBusiness CA-2 SHA1 Fingerprint: 39:4F:F6:85:0B:06:BE:52:E5:18:56:CC:10:E1:80:E8:82:B3:85:CC As per Bug #847604, turn off the websites and code signing trust bits for the following two root certs. Only the email trust bit should be enabled for both of these root certs. Friendly name: Digital Signature Trust Co. Global CA 1 OU = DSTCA E1 O = Digital Signature Trust Co. SHA1 Fingerprint: 81:96:8B:3A:EF:1C:DC:70:F5:FA:32:69:C2:92:A3:63:5B:D1:23:D3 Friendly name: Digital Signature Trust Co. Global CA 3 OU = DSTCA E2 O = Digital Signature Trust Co. SHA1 Fingerprint:AB:48:F3:33:DB:04:AB:B9:C0:72:DA:5B:0C:C1:D0:57:F0:36:9B:46 As per Bug #850740, turn off all three trust bits for the following root cert: CN = TC TrustCenter Universal CA III OU = TC TrustCenter Universal CA O = TC TrustCenter GmbH SHA1 Fingerprint: 96:56:CD:7B:57:96:98:95:D0:E1:41:46:68:06:FB:B8:C6:11:06:87
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 with a fresh profile, and confirm the changes listed above. Thanks! Kathleen
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.