Closed Bug 722843 Opened 10 years ago Closed 9 years ago
Turn on code signing trust bit for thawte Primary Root CA
This bug requests a change to the trust bit settings for the “thawte Primary Root CA” root certificate, owned by Symantec. This root certificate is already included in NSS. The requested change is to turn on the codes signing trust bit. Friendly name: thawte Primary Root CA SHA1 Fingerprint: 91:C6:D6:EE:3E:8A:C8:63:84:E5:48:C2:99:29:5C:75:6C:81:7B:81 Trust flags: Websites, Code This CA has been assessed in accordance with the Mozilla project guidelines, and the requested changes approved in bug #601950. The steps are as follows: 1) A representative of the CA must confirm that all the data in this bug is correct. 2) A Mozilla representative creates a patch with the requested changes, 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 correct trust bits are turned on for this certificate. 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 changes. This process is mostly under the control of the release drivers for those products.
Rick, Please see step #1 above.
Severity: normal → enhancement
All the data in this bug 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.
The test build is available at http://email@example.com/ or from http://kuix.de/mozilla/tryserver-roots-20120604/ Can a CA representative please verify the trust settings for correctness? (see initial comments in this bug, and you should make sure 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.)
The trust settings are correct. I verified them with /firstname.lastname@example.org/try-win32. Thanks!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: In FF16
Target Milestone: --- → 3.13.6
You need to log in before you can comment on or make changes to this bug.