Closed Bug 768547 Opened 10 years ago Closed 9 years ago
Add new TURKTRUST root certificate to NSS
This bug requests inclusion in the NSS root certificate store of the following certificate, owned by TÜRKTRUST. Friendly name: TÜRKTRUST Elektronik Sertifika Hizmet Sağlayıcısı Certificate location: http://www.turktrust.com.tr/sertifikalar/TURKTRUST_Elektronik_Sertifika_Hizmet_Saglayicisi_s3.crt SHA1 Fingerprint: F1:7F:6F:B6:31:DC:99:E3:A3:C8:7F:FE:1C:F1:81:10:88:D9:60:33 Trust flags: Websites, Code Signing Test URL: https://evssl.turktrust.com.tr This CA has been assessed in accordance with the Mozilla project guidelines, and the certificates approved for inclusion in bug #433845. 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.
Mert, Please see step #1 above.
For Step 1: As a representative of TURKTRUST, I confirm that all the data in this bug is correct and the correct certs have been attached. For Step 3: As a representative of TURKTRUST, we have used the test version of Firefox namely Minefield and we have shown the green bar for our test site by following the steps in PSM EV Testing. Moreover, we have attached the snapshot to the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=433845
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-20121004/ 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.)
(In reply to Kai Engert (:kaie) from comment #4) > Can a CA representative please verify the trust settings for correctness? Here are instructions about how to perform this testing: https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion
As the official representative of TURKTRUST, I confirm that the trust settings are correct for our root cert.
fixed in bug 795355
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.14
TurkTrust has completed the action items in bug #835538, so we may proceed with inclusion of this root certificate.
(In reply to Kathleen Wilson from comment #0) > > Friendly name: TÜRKTRUST Elektronik Sertifika Hizmet Sağlayıcısı A minor issue: I don't like this friendly name, because this identical name is used as the "common name" in all root CA certificates used by Turktrust, in both the existing ones and the new one! I think we should avoid confusion and use a friendly name that better describes the new root. For the existing two certificates, we had used the following friendly names: - TURKTRUST Certificate Services Provider Root 1 - TURKTRUST Certificate Services Provider Root 2 For the new one, I propose we use: - TURKTRUST Certificate Services Provider Root 2007 Note the friendly name is simply used as a technical identifier.
That makes sense. I agree with the friendly name you proposed. Thanks, Kathleen
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://firstname.lastname@example.org/ 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 cert is 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 root is included and the correct trust bits set. https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion
As a representative of TURKTRUST, I have used "Nightly" given with a brand new profile to confirm the new root cert is included with the correct trust bits set. (My demo site for this test was "https://support.btc-ag.com.tr/support") Thanks ...
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Target Milestone: 3.14 → 3.15
You need to log in before you can comment on or make changes to this bug.