Closed Bug 823766 Opened 13 years ago Closed 12 years ago

Turn on code signing trust bit for TWCA Root Certification Authority certificate

Categories

(NSS :: CA Certificates Code, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kathleen.a.wilson, Assigned: KaiE)

References

Details

(Whiteboard: test complete)

This bug requests that the code signing trust bit be turned on for the following certificate, owned by TWCA. CN = TWCA Root Certification Authority SHA1 Fingerprint: CF:9E:87:6D:D3:EB:FC:42:26:97:A3:B5:A3:7A:A0:76:A9:06:23:48 Trust flags: Websites, Email, Code Signing Test URL: https://evssldemo.twca.com.tw/index.html The TWCA CA has been assessed in accordance with the Mozilla project guidelines, and this certificate approved for inclusion in bug #745671. The next 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 to turn on the code signing trust bit, 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 change. This process is mostly under the control of the release drivers for those products.
Robin, Please see step #1 above.
I have verified that 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.
Depends on: 857615
Assignee: nobody → kaie
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://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/kaie@kuix.de-cdb68506e138/ 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 that all three trust bits are now enabled for the "TWCA Root Certification Authority" root cert. A representative of the CA needs to also confirm that they have installed the test build and verified that the correct trust bits are set. https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion
I used nightly build with new profile to check the trust bits. When I use certificate viewer to view build in object, it only display "SSL Certificate Authority". I use edit trust to view the trust setting, the 3 trust bits are enabled by default. Is it correct?
(In reply to Robin Lin from comment #6) > I used nightly build with new profile to check the trust bits. > When I use certificate viewer to view build in object, it only display "SSL > Certificate Authority". I think that your profile (cert8.db file) hadn't been reset at that point. Currently this root cert has both the SSL and email trust bits set, so you must have previously over-ridden the default settings. > I use edit trust to view the trust setting, the 3 > trust bits are enabled by default. > Is it correct? Hmmm. That is interesting. I guess your profile got reset by the time you did this part of the test. This is the expected result, since this request is to also enable the code signing trust bit, and the other two trust bits were already enabled.
Whiteboard: test complete
Target Milestone: --- → 3.15
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.