1320783 - Add Symantec Class 1 and Class 2 certificates to NSS

Status: RESOLVED FIXED

(NSS :: CA Certificates Code, task)

Description

[Kathleen Wilson]

This bug requests inclusion in the NSS root store of the following root certificates owned by Symantec.

Friendly Name: Symantec Class 1 Public Primary Certification Authority - G6
Cert Location: https://www.symantec.com/content/en/us/enterprise/verisign/roots/PCA_1_G6.pem
SHA-1 Fingerprint: 51:7F:61:1E:29:91:6B:53:82:FB:72:E7:44:D9:8D:C3:CC:53:6D:64
SHA-256 Fingerprint: 9D:19:0B:2E:31:45:66:68:5B:E8:A8:89:E2:7A:A8:C7:D7:AE:1D:8A:AD:DB:A3:C1:EC:F9:D2:48:63:CD:34:B9
Trust Flags: Email

Friendly Name: Symantec Class 2 Public Primary Certification Authority - G6
Cert Location: https://www.symantec.com/content/en/us/enterprise/verisign/roots/PCA_2_G6.pem
SHA-1 Fingerprint: 40:B3:31:A0:E9:BF:E8:55:BC:39:93:CA:70:4F:4E:C2:51:D4:1D:8F
SHA-256 Fingerprint: CB:62:7D:18:B5:8A:D5:6D:DE:33:1A:30:45:6B:C6:5C:60:1A:4E:9B:18:DE:DC:EA:08:E7:DA:AA:07:81:5F:F0
Trust Flags:Email
Example Cert: https://ssltest37.ssl.symclab.com/

Friendly Name: Symantec Class 1 Public Primary Certification Authority - G4
Cert Location: https://www.symantec.com/content/en/us/enterprise/verisign/roots/Symantec_Class_1_Public_Primary_Certification_Authority_G4.pem
SHA-1 Fingerprint: 84:F2:E3:DD:83:13:3E:A9:1D:19:52:7F:02:D7:29:BF:C1:5F:E6:67
SHA-256 Fingerprint: 36:3F:3C:84:9E:AB:03:B0:A2:A0:F6:36:D7:B8:6D:04:D3:AC:7F:CF:E2:6A:0A:91:21:AB:97:95:F6:E1:76:DF
Trust Flags: Email
	 
Friendly Name: Symantec Class 2 Public Primary Certification Authority - G4
Cert Location: https://www.symantec.com/content/en/us/enterprise/verisign/roots/Symantec_Class_2_Public_Primary_Certification_Authority_G4.pem
SHA-1 Fingerprint: 67:24:90:2E:48:01:B0:22:96:40:10:46:B4:B1:67:2C:A9:75:FD:2B
SHA-256 Fingerprint: FE:86:3D:08:22:FE:7A:23:53:FA:48:4D:59:24:E8:75:65:6D:3D:C9:FB:58:77:1F:6F:61:6F:9D:57:1B:C5:92
Trust Flags: Email

This CA has been assessed in accordance with the Mozilla project guidelines, and the certificates approved for inclusion in bug #833986. 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.
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: Class1G6RootCert.cert

Comment 2

[Kathleen Wilson]

Attachment: Class2G6RootCert.cert

Comment 3

[Kathleen Wilson]

Attachment: Class1G4RootCert.cert

Comment 4

[Kathleen Wilson]

Attachment: Class1G6RootCert.cert

Comment 5

[Kathleen Wilson]

Steve or Rick, Please see step #1 above.

Comment 6

[Steven Medin]

Kathleen, the first three attachments are correct but the fourth attachment duplicates the C1-G6 so we're missing the C2-G4.

All links and hashes validate to our internal database for all four roots. Hashes validate to your attachments for the first three entries.

Under C2-G6, there is a link that is not relevant: 
Example Cert: https://ssltest37.ssl.symclab.com/

Comment 7

[Kathleen Wilson]

Attachment: Class2G4RootCert.cert

Comment 8

[Kathleen Wilson]

(In reply to Steven Medin from comment #6)
> Kathleen, the first three attachments are correct but the fourth attachment
> duplicates the C1-G6 so we're missing the C2-G4.

Fixed. Please double-check...

Comment 9

[Steven Medin]

C2-G4 confirmed correct, hashes match.  All data verifies.

Comment 10

[Kathleen Wilson]

Thanks!

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 11

[Kathleen Wilson]

(In reply to Kathleen Wilson from comment #0)
> 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.

The test build for this change is here:
https://archive.mozilla.org/pub/firefox/try-builds/[e-mail]-0ff968e3d09e43aa1186a83d9df1b0159adf61e0/

Steven, please test that the correct root certificates have been added, and that the correct trust bit is set, as described here:
https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion

Comment 12

[Rick Andrews]

We have confirmed steps 1-4 of the Testing Inclusion process. Step 5 doesn't apply since these roots are not used to issue SSL/TLS certs. Thank you.