This bug requests inclusion in the NSS root store of the following root certificates owned by Autoridad de Certificacion Firmaprofesional. Friendly Name: Autoridad de Certificacion Firmaprofesional CIF A62634068 Cert Location: http://crl.firmaprofesional.com/caroot256.crt SHA-1 Fingerprint: 0BBEC2272249CB39AADB355C53E38CAE78FFB6FE SHA-256 Fingerprint: 57DE0583EFD2B26E0361DA99DA9DF4648DEF7EE8441C3B728AFA9BCDE0F9B26A Trust Flags: Email; Websites Test URL: https://www.firmaprofesional.com This CA has been assessed in accordance with the Mozilla project guidelines, and the certificates approved for inclusion in bug #1102143 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. 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 certificate. This process is mostly under the control of the release drivers for those products.
Bug 1741930 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This bug requests inclusion in the NSS root store of the following root certificates owned by Autoridad de Certificacion Firmaprofesional. Friendly Name: Autoridad de Certificacion Firmaprofesional CIF A62634068 Cert Location: http://crl.firmaprofesional.com/caroot256.crt SHA-1 Fingerprint: 0BBEC2272249CB39AADB355C53E38CAE78FFB6FE SHA-256 Fingerprint: 57DE0583EFD2B26E0361DA99DA9DF4648DEF7EE8441C3B728AFA9BCDE0F9B26A Trust Flags: Email; Websites Test URL: https://testsslev2021.firmaprofesional.com This CA has been assessed in accordance with the Mozilla project guidelines, and the certificates approved for inclusion in bug #1102143 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. 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 certificate. This process is mostly under the control of the release drivers for those products.