This bug requests inclusion in the NSS root certificate store of the following certificate, owned by Deutscher Sparkassen Verlag GmbH (DSV-Gruppe, S-TRUST). Friendly Name: S-TRUST Universal Root CA Cert Location: https://www.s-trust.de/ablage_download_dokumente/ablage_zertifikate/S-TRUST_Universal_Root_CA1.cer SHA-1 Fingerprint: 1B:3D:11:14:EA:7A:0F:95:58:54:41:95:BF:6B:25:82:AB:40:CE:9A Trust Flags: Email Example Cert: https://bugzilla.mozilla.org/attachment.cgi?id=8506014 This CA has been assessed in accordance with the Mozilla project guidelines, and the certificate approved for inclusion in bug #1011182. 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 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 certificates. This process is mostly under the control of the release drivers for those products.
Alexandru, Please see step #1 above.
I can confirm that all the data in this bug is correct. Best regards, Alexandru
Test builds of a development version of Firefox, which contain the requested change(s), can be found here: https://email@example.com/
Alexandru, Please check the code change as described here: https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion (except for step #5, since the Websites trust bit is not enable for this root)
Kathleen, I checked the changes as described here: https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion (except for step 5) I can confirm that the certificate is marked as "Builtin Object Token" in the Security Device column and the correct trust bits (E-Mail) are checked. Best regards, Alexandru