823753 - Add Disig Root R1 and Disig Root R2 certificates to NSS

Status: RESOLVED FIXED

(NSS :: CA Certificates Code, task)

Description

[Kathleen Wilson]

This bug requests inclusion in the NSS CA certificate store of the following certificate, owned by Disig.

Friendly name: CA Disig Root R1
Certificate location: http://www.disig.sk/rootcar1/cert/rootcar1.der
SHA1 Fingerprint: 8E:1C:74:F8:A6:20:B9:E5:8A:F4:61:FA:EC:2B:47:56:51:1A:52:C6
Trust flags: Websites, Email, Code Signing
Test URL: https://testssl-valid-r1i1.disig.sk

Friendly name: CA Disig Root R2
Certificate location: http://www.disig.sk/rootcar2/cert/rootcar2.der
SHA1 Fingerprint: B5:61:EB:EA:A4:DE:E4:25:4B:69:1A:98:A5:57:47:C2:34:C7:D9:71
Trust flags: Websites, Email, Code Signing
Test URL: https://testssl-valid-r2i1.disig.sk 

The Disig CA has been assessed in accordance with the Mozilla project guidelines, and these certificates approved for inclusion in bug #792377.

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 works 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.

Comment 1

[Kathleen Wilson]

Attachment: CA Disig Root R1 cert

Comment 2

[Kathleen Wilson]

Attachment: CA Disig Root R2 cert

Comment 3

[Kathleen Wilson]

Peter, Please see step #1 above.

Comment 4

[Peter Miskovic]

On behalf of CA Disig Certification Authority I can confirm that all data in this bug are correct and attached certificate are also correct.
Regards,
Peter Miskovic
Policy Management Authority member
Certification Authority CA Disig
 
Disig, a. s.
Zahradnicka 151, 821 08 Bratislava 2, Slovakia
phone. [phone]
[e-mail]
www.disig.eu

Comment 5

[Kathleen Wilson]

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.

Comment 6

[Kai Engert (: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/[e-mail]-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 )

Comment 7

[Kathleen Wilson]

I have used the test build and a fresh profile to confirm the new root certs are 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 roots are included and the correct trust bits set. https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion

Comment 8

[Peter Miskovic]

We used the test build and a fresh profile on three different platforms (Windows, Linux and MacOSX) and we can confirm that our two new roots (CA Disig Root R1 and CA Disig Root R2) are correct and included with the correct trust bits set. We also tested connection to our test sites for this new roots and we got correct basic domain validation status for all three testing scenarios (valid, revoked and expired SSL certificates).