915935 - Add E-Tugra Certification Authority root certificate to NSS

Status: RESOLVED FIXED

(NSS :: CA Certificates Code, task)

Description

[Kathleen Wilson]

Attachment: Renewed_Etugra_Root.crt

This bug requests inclusion in the NSS root certificate store of the following certificate, owned by E-Tugra.

Friendly name: E-Tugra Certification Authority
Certificate location: http://www.e-tugra.com.tr/crt/Etugra_Root.crt
SHA1 Fingerprint: 51:C6:E7:08:49:06:6E:F3:92:D4:5C:A0:0D:6D:A3:62:8F:C3:52:39
Trust flags: Websites, Code Signing
Test URL: https://sslev.e-tugra.com.tr/

This CA has been assessed in accordance with the Mozilla project guidelines, and the certificates approved for inclusion in bug #877744.

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 certificate has been attached.

2) A Mozilla representative creates a patch with the new certificate, 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 certificate has 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 certificate. This process is mostly under the control of the release drivers for those products.

Comment 1

[Kathleen Wilson]

Davut, Please see step #1 above.

Comment 2

[Davut Tokgöz]

We confirm that the information given above and the certificate attached to the bug are correct.

Comment 3

[Davut Tokgöz]

I want to note that we used www.e-tugra.com instead of www.e-tugra.com.tr inside certificates, even they both www.e-tugra.com and www.e-tugra.com.tr refer to the same place. So we can set http://www.e-tugra.com/crt/Etugra_Root.crt instead of http://www.e-tugra.com.tr/crt/Etugra_Root.crt as certificate location, if this must be same with the value inside intermediate certificates.

Comment 4

[Kathleen Wilson]

(In reply to Davut Tokgöz from comment #3)
> I want to note that we used www.e-tugra.com instead of www.e-tugra.com.tr
> inside certificates, even they both www.e-tugra.com and www.e-tugra.com.tr
> refer to the same place. So we can set
> http://www.e-tugra.com/crt/Etugra_Root.crt instead of
> http://www.e-tugra.com.tr/crt/Etugra_Root.crt as certificate location, if
> this must be same with the value inside intermediate certificates.

I don't think it matters.

Comment 5

[Kathleen Wilson]

(In reply to Davut Tokgöz from comment #2)
> We confirm that the information given above and the certificate attached to
> the bug are correct.

Thanks for confirming that the data in this bug is correct.

Root inclusions 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.

Comment 6

[Davut Tokgöz]

Hi, is there anything that we have to do for this bug?  We are waiting the test instructions.

Comment 7

[Kathleen Wilson]

We will update this bug when a test build with the corresponding code change is available. At that time, we will ask you to test that the correct changes have been made.

Comment 8

[Kathleen Wilson]

Please test that your root has been correctly included, that the trust bits are set correctly, and that connections to your test site work with basic domain validation status.

EV-enablement 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/[e-mail]-e9ed86288188/

Download a binary for your preferred operating system, you probably want one of the following files:
  try-linux/firefox-....en-US.linux-i686.tar.bz2
  try-linux64/firefox-....en-US.linux-x86_64.tar.bz2
  try-macosx64/firefox-....en-US.mac.dmg
  try-win32/firefox-....en-US.win32.zip

Please follow the test instructions here:
https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion

Make sure you use a fresh profile for your testing.
http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Comment 9

[Davut Tokgöz]

We tested successfully on Windows platform and Macos. 
* Both builds identify our test site https://sslev.e-tugra.com.tr 
* Both builds includes new root and the website and code-signing bits are set. Each test are done fresh installation of OS and naturally with fresh profile.

Comment 10

[Davut Tokgöz]

we also tested on Linux  and 64 bit Linux with successfully. The root is included and test site is browsed.

Comment 11

[Kathleen Wilson]

Thanks for testing.
We are targeting Firefox 29 for this change.
https://wiki.mozilla.org/RapidRelease/Calendar

Comment 12

[Davut Tokgöz]

Thank you for your good news

Comment 13

[Kai Engert [:KaiE:]]

done as part of bug 957300