CA/Dashboard: Difference between revisions
(Temporary work-around regarding Bug #1412570 -- removed the include_fields lines) |
(include_fields has to be an array now) |
||
| Line 12: | Line 12: | ||
"status":["UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED"], | "status":["UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED"], | ||
"whiteboard":"ca-initial", | "whiteboard":"ca-initial", | ||
"cf_blocking_b2g_type":"contains" | "cf_blocking_b2g_type":"contains", | ||
"include_fields": ["id", "summary", "status", "assigned_to", "whiteboard", "last_change_time"] | |||
} | } | ||
</bugzilla> | </bugzilla> | ||
Revision as of 23:39, 30 October 2017
Dashboard for Certificate Change Requests
When Mozilla receives a request for a change to our Root Store, the request passes through the stages outlined below.
To Be Assigned
This section lists CAs who have applied for inclusion but Mozilla has not yet started processing their applications. Action needed by: Mozilla and/or CA.
| ID | Summary | Status | Assigned to | Whiteboard | Last change time |
|---|---|---|---|---|---|
| 1736904 | Add Algerian National Root CA certificate | ASSIGNED | Ben Wilson | [ca-initial] [ccadb-case-00001010] | 2025-12-02T04:53:37Z |
| 1748579 | Add Aspire root certificates | ASSIGNED | Ben Wilson | [ca-initial] [ccadb-case-00000888] | 2025-12-02T04:55:42Z |
| 1870013 | Add Saudi National SSL root CA | ASSIGNED | Ben Wilson | [ca-initial] [ccadb-case-00001657] | 2025-12-02T04:46:46Z |
| 1883983 | Add SOLUTI GLOBAL ROOT CA | ASSIGNED | Ben Wilson | [ca-initial] [ccadb-case-00001713] | 2025-12-02T04:48:22Z |
| 1978757 | Add VIDA CA Root | ASSIGNED | Ben Wilson | [ca-initial] [ccadb-case-00002622] | 2025-12-02T04:49:44Z |
| 1978904 | Add NETLOCK's S/MIME & TLS Root | ASSIGNED | Ben Wilson | [ca-initial] [ccadb-case-00002590] | 2025-12-02T04:42:12Z |
| 1983217 | Add Aretiico Group PLC and Aretiico Inc root certificates to Mozilla Root store | ASSIGNED | Ben Wilson | [ca-initial] [ccadb-case-00002626] | 2025-12-02T04:48:59Z |
| 2001274 | Add Cybertrust Japan Root CA Cybertrust iTrust TLS ECCP384 Root CA 2025 | ASSIGNED | Ben Wilson | [ca-initial] | 2025-11-21T17:37:05Z |
| 2001275 | Add Cybertrust Japan Root CA Cybertrust iTrust TLS RSA4096 Root CA 2025 | ASSIGNED | Ben Wilson | [ca-initial] | 2025-11-21T17:37:24Z |
9 Total; 9 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Information Verification
This section lists CAs who are in the process of having the information provided in their application verified as complete and correct by Mozilla, which will involve a dialog between the two parties. Action needed by: Mozilla and/or CA.
17 Total; 17 Open (100%); 0 Resolved (0%); 0 Verified (0%);
On Hold (Super CA)
This section lists CAs who have been judged to be "Super CAs". Super CAs need to have all their sub-CAs apply for inclusion and be accepted before their application can progress. Action needed by: CA.
| ID | Summary | Priority | Status |
|---|---|---|---|
| 1449941 | Add Fina Root CA certificate | P4 | ASSIGNED |
| 1565871 | Add CCA ROOT CA India | P5 | ASSIGNED |
| 1592138 | Add Macao Post eSignTrust root certificate | P3 | ASSIGNED |
| 1674669 | Add Autoridade Certificadora Raiz Brasileira root certificate | P5 | ASSIGNED |
4 Total; 4 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Ready for Public Discussion
This section lists CAs for whom the information verification phase is complete, and the next stage is for Mozilla to begin a public discussion in the mozilla.dev.security.policy group about the merits of their inclusion. Action needed by: Mozilla.
To see the approximate order in which discussions may be started (after the BR Self Assessment has been provided by the CA and verified by Mozilla):
- Click on the "Whiteboard" column to sort
- Whiteboard tags with "-new" indicate that the CA does not currently have a root certificate in Mozilla's program.
- Whiteboard tags without "-new" indicate that the CA already has a root certificate in Mozilla's program, so they have previously been through Mozilla's rigorous vetting process, and will be given priority in the discussions.
- In general:
- Discussions will be started according to the date when the bug became ready for discussion (the date listed in the whiteboard); i.e. the oldest date will typically be the next discussion to start.
- Only one or two of the "-new" requests may be in discussion at any given point. The amount of time that each discussion takes varies dramatically depending on the number of reviewers contributing to the discussion, and the types of concerns that are raised.
- Requests that are from CAs that already have roots included in NSS may be discussed in parallel, so several of these discussions can happen at the same time.
| ID | Summary | Priority | Status |
|---|---|---|---|
| 1845081 | Add MOIS SSL Root CA | P2 | ASSIGNED |
| 1925173 | Add Cybertrust Japan SecureSign Root CA16 | P2 | ASSIGNED |
| 1941966 | SECOM: New Subordinate CA Request (JPRS) | P1 | ASSIGNED |
3 Total; 3 Open (100%); 0 Resolved (0%); 0 Verified (0%);
In Public Discussion
This section lists CAs whose inclusion is currently being publicly discussed. Action needed by: Public and CA.
| ID | Summary | Priority | Status |
|---|---|---|---|
| 1873057 | Add Microsec "e-Szigno TLS Root CA 2023" | P2 | ASSIGNED |
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Discussions On Hold
This section lists CAs for whom the public discussion concluded with action items for the CA to complete, and the CA has not yet completed the action items. Once the action items are completed, discussion can restart. Action needed by: CA.
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Pending Approval
This section lists CAs for which public discussion has been completed, but have not yet been approved by Mozilla for inclusion. Action needed by: Mozilla.
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Approved and Pending Code Changes
This section lists CAs who have been approved and are waiting for Mozilla to add their certificates to the root store file. Action needed by: Mozilla.
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);