Add ISRG Root X1 root certificate to NSS

RESOLVED FIXED in 3.26

Status

NSS
CA Certificates Code
--
enhancement
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: Kathleen Wilson, Unassigned)

Tracking

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

1.92 KB, application/x-x509-ca-cert
Details
(Reporter)

Description

2 years ago
Created attachment 8775296 [details]
ISRGRootX1.cert

This bug requests inclusion in the NSS root store of the following root certificate owned by Internet Security Research Group (ISRG)
	 
Friendly Name: ISRG Root X1
Cert Location: https://letsencrypt.org/certs/isrgrootx1.der
SHA-1 Fingerprint: CA:BD:2A:79:A1:07:6A:31:F2:1D:25:36:35:CB:03:9D:43:29:A5:E8
SHA-256 Fingerprint: 96:BC:EC:06:26:49:76:F3:74:60:77:9A:CF:28:C5:A7:CF:E8:A3:C0:AA:E1:1A:8F:FC:EE:05:C0:BD:DF:08:C6
Trust Flags: Websites
Test URL: https://helloworld.letsencrypt.org/

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

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.
(Reporter)

Comment 1

2 years ago
Josh, Please see step #1 above.

Comment 2

2 years ago
(In reply to Kathleen Wilson from comment #0)

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

I confirm that all of the information in this bug's description is correct and that the correct certificate is attached.

Updated

2 years ago
Depends on: 1290999
(Reporter)

Comment 3

2 years ago
Josh,

Test build info is here: https://bugzilla.mozilla.org/show_bug.cgi?id=1290999#c3

To test the addition of the ISRG Root X1, please provide a URL to a test site whose SSL cert chains up to this root, and not the "DST Root CA X3" root.

Then please test as described here: https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion

Be sure to use the test build, create a new user profile, and turn off trust for the "DST Root CA X3" root cert.
(Reporter)

Comment 4

2 years ago
According to https://bugzilla.mozilla.org/show_bug.cgi?id=1290999#c9 
"The Let's Encrypt team has tested the build with our root added on multiple platforms (Linux, OS X, Windows) and everything seems to work well."

I have also used the test build to confirm that the patch to add the "DST Root CA X3" root is correct and has only the Websites trust bit set.
(Reporter)

Comment 5

2 years ago
(In reply to Kathleen Wilson from comment #4)
> According to https://bugzilla.mozilla.org/show_bug.cgi?id=1290999#c9 
> "The Let's Encrypt team has tested the build with our root added on multiple
> platforms (Linux, OS X, Windows) and everything seems to work well."
> 
> I have also used the test build to confirm that the patch to add the "DST
> Root CA X3" root is correct and has only the Websites trust bit set.

Copy-paste error, meant to say:
I have also used the test build to confirm that the patch to add the "ISRG Root X1" root is correct and has only the Websites trust bit set.

Comment 6

2 years ago
fixed, see bug 1290999 for the commit(s).
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.26
You need to log in before you can comment on or make changes to this bug.