1972384 - Add TrustAsia Dedicated Roots to NSS

Status: RESOLVED DUPLICATE of bug 1972391

(NSS :: CA Certificates Code, task)

Description

[incident-reporting]

This bug requests inclusion in the NSS root store of the following root certificates owned by TrustAsia Technologies, Inc.:

Root Certificate 1 of 4
Friendly Name: TrustAsia SMIME ECC Root CA
Cert Location: https://repository.trustasia.com/repo/certs/dedicated/TrustAsiaSMIMEECCRootCA.cer
SHA-1 Fingerprint: 8C0DAAFE13FA59F2DB9D0C97DA12A2451A021354
SHA-256 Fingerprint: 436472C1009A325C54F1A5BBB5468A7BAEECCBE05DE5F099CB70D3FE41E13C16
Trust Flags: Email

Root Certificate 2 of 4
Friendly Name: TrustAsia SMIME RSA Root CA
Cert Location: https://repository.trustasia.com/repo/certs/dedicated/TrustAsiaSMIMERSARootCA.cer
SHA-1 Fingerprint: 8C69217CCE4973365A5CEF2BB0869750E3E33365
SHA-256 Fingerprint: C7796BEB62C101BB143D262A7C96A0C6168183223EF50D699632D86E03B8CC9B
Trust Flags: Email

Root Certificate 3 of 4
Friendly Name: TrustAsia TLS ECC Root CA
Cert Location: https://repository.trustasia.com/repo/certs/dedicated/TrustAsiaTLSECCRootCA.cer
SHA-1 Fingerprint: B5EC39F3A16637AEC3059457E2BE11BEB7A17F36
SHA-256 Fingerprint: C0076B9EF0531FB1A656D67C4EBE97CD5DBAA41EF44598ACC2489878C92D8711
Trust Flags: Websites
Test URL: https://ev-ecctls-valid.trustasia.com

Root Certificate 4 of 4
Friendly Name: TrustAsia TLS RSA Root CA
Cert Location: https://repository.trustasia.com/repo/certs/dedicated/TrustAsiaTLSRSARootCA.cer
SHA-1 Fingerprint: A54650C562EA959A1AA7046F1758C729533D03FA
SHA-256 Fingerprint: 06C08D7DAFD876971EB1124FE67F847EC0C7A158D3EA53CBE940E2EA9791F4C3
Trust Flags: Websites
Test URL: https://ev-rsatls-valid.trustasia.com

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

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 are referenced.
2. A Mozilla representative creates a patch with the new certificates.
3. The Mozilla representative requests that another Mozilla representative review the patch.
4. The Mozilla representative adds (commits) the patch to NSS, then closes this bug as RESOLVED FIXED.
5. 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.