Closed Bug 1683738 Opened 11 months ago Closed 9 months ago

Add AC RAIZ FNMT-RCM SERVIDORES SEGUROS root cert to NSS

Categories

(NSS :: CA Certificates Code, task, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kwilson, Assigned: beurdouche)

References

Details

(Whiteboard: March 2021 Batch of Root Changes)

Attachments

(2 files)

This bug requests inclusion in the NSS root store of the following root certificates owned by Government of Spain, Fábrica Nacional de Moneda y Timbre (FNMT).

Friendly Name: AC RAIZ FNMT-RCM SERVIDORES SEGUROS
Cert Location: https://www.sede.fnmt.gob.es/documents/10445900/10526749/AC_Raiz_FNMT-RCM-SS.cer
SHA-1 Fingerprint: 62FFD99EC0650D03CE7593D2ED3F2D32C9E3E54A
SHA-256 Fingerprint: 554153B13D2CF9DDB753BFBE1A4E0AE08D0AA4187058FE60A2B862B2E4B87BCB
Trust Flags: Websites
Test URL: https://testactivetipo1.cert.fnmt.es/

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

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.

Santiago, Please see step #1 above.

Thank you Kathleen. All the above data as well as the attached certificate are correct.

Blocks: 1683761
Depends on: 1693217
Assignee: nobody → bbeurdouche
Severity: -- → S1
Status: NEW → ASSIGNED
Type: enhancement → task
Priority: -- → P1
Target Milestone: --- → 3.63
Status: ASSIGNED → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.