Add NETLOCK ECC Root

Netlock requested inclusion of a new ECC-based root certificate in Mozilla’s CA Certificate Root Program. The request was triggered by Netlock’s decision to set up a new CA based on the ECC algorithm and to include it in the root program. Netlock stated the certificate had been tested in its 2022 conformity assessment audit by MATRIX Tanúsító Ltd. and that it was included in the Audit Attestation letter. Mozilla added the root certificate to the CCADB, and Netlock was asked to complete the CCADB information for the new root CA record. Later, Netlock said it could not provide the mandatory services infrastructure (e.g., CRL and OCSP) for the new root certificates due to supply chain constraints and slow procurement, and it planned to close the enrolment tickets until hardware was procured. In 2024, Netlock indicated it did not want to pursue this inclusion request and would close it, stating it would submit a different root for inclusion. The bug was resolved as WONTFIX.

1. 2022-10-11 Netlock submitted an inclusion request for a new ECC root certificate (NETLOCK Root CA ECC) for the Mozilla root program.
2. 2022-10-12 Mozilla added the requested root certificate to the CCADB and asked Netlock to complete CCADB information for the new root CA record.
3. 2023-01-24 Netlock reported it was unable to provide mandatory services infrastructure for the new root certificates and asked how to handle the open tickets.
4. 2024-01-24 Netlock requested closing the inclusion request and said it would submit a different root for inclusion.

1. 2022-10-11 Netlock — Netlock requested inclusion of the new ECC root certificate and stated it was included in the 2022 audit attestation letter.
2. 2022-10-12 Mozilla representative — Mozilla added the root certificate to the CCADB and said Netlock must complete CCADB information for the new root CA record.
3. 2023-01-24 Netlock — Netlock said supply chain constraints prevented procurement of required hardware for mandatory services (e.g., CRL/OCSP) and asked whether to set the tickets to INVALID or take another action.
4. 2023-01-24 Mozilla representative — Mozilla suggested leaving the ticket open and noting a holding pattern, and asked whether period-of-time audits would remain continuously in place.
5. 2024-01-08 Mozilla representative — Mozilla asked whether Netlock wanted to pursue the inclusion request.
6. 2024-01-24 Netlock — Netlock replied that it wanted to close the request and would submit a different root for inclusion.