Add Microsec's "e-Szigno Root CA 2017" root certificate to NSS
Categories
(NSS :: CA Certificates Code, enhancement, P1)
Tracking
(Not tracked)
People
(Reporter: kathleen.a.wilson, Assigned: jcj)
References
Details
Attachments
(3 files)
This bug requests inclusion in the NSS root store of the following root certificate owned by Microsec Ltd..
Friendly Name: e-Szigno Root CA 2017
Cert Location: http://www.e-szigno.hu/rootca2017.crt
SHA-1 Fingerprint: 89D483034F9E9A48805F7237D4A9A6EFCB7C1FD1
SHA-256 Fingerprint: BEB00B30839B9BC32C32E4447905950641F26421B15ED089198B518AE2EA1B99
Trust Flags: Email; Websites
Test URL: https://eqtlsca2018-valid.e-szigno.hu/
This CA has been assessed in accordance with the Mozilla project guidelines, and the certificates approved for inclusion in bug #1445364
The next steps are as follows:
- A representative of the CA must confirm that all the data in this bug is correct, and that the correct certificates have been attached.
- A Mozilla representative creates a patch with the new certificates, and provides a special test version of Firefox.
- 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 work correctly.
- The Mozilla representative requests that another Mozilla representative review the patch.
- The Mozilla representative adds (commits) the patch to NSS, then closes this bug as RESOLVED FIXED.
- 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.
Assignee | ||
Comment 2•4 years ago
|
||
Comment on attachment 9156045 [details]
e-SzignoRootCA2017.pem
This is PEM-encoded, decoding to DER and re-attaching
Assignee | ||
Comment 3•4 years ago
|
||
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 4•4 years ago
|
||
Depends on D79371
Comment 5•4 years ago
|
||
On behalf of Microsec, I confirm that all the data in this bug is correct, and that the correct certificate has been attached.
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Description
•