CA/Dashboard: Difference between revisions

Jump to navigation Jump to search

CA/Dashboard (view source)

Revision as of 16:53, 4 May 2017

1,224 bytes removed ,  4 May 2017
Slim down
(Bugzilla Product/Component updated for CA Program Bugs)
(Slim down)
Line 1: Line 1:
= Dashboard for CA Inclusion/Update Requests =
__NOTOC__
CAs are parties who are trusted to attest to the identity of websites. Mozilla has a rigorous process for CAs to request inclusion of their certificates, the details of which are described in the following:
= Dashboard for Certificate Change Requests =
* [[CA|Process Overview]]
* [http://www.mozilla.org/projects/security/certs/policy/ Mozilla CA Certificate Policy]
* [[CA:FAQ | General Background and FAQ on CAs and the Mozilla process]]
* [[CA:How_to_apply | CA Inclusion Process in detail]]
* [[CA:Overview | Other useful information]]
* [[CA_Bug_Triage#CA_Program_Whiteboard_Tags|CA Program Bugzilla whiteboard tags]]


= To Be Assigned =
When Mozilla receives a request for a change to our Root Store, the request passes through the stages outlined below.
When the whiteboard says "[ca-initial] -- OK to begin Information Verification", that means that it is ready for someone to begin the Information Verification. If you are able to do the Information Verification for the bug, then assign the bug to yourself, CC Kathleen on the bug, and update the whiteboard.
 
== 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'''.


<bugzilla>
<bugzilla>
Line 21: Line 18:
</bugzilla>
</bugzilla>


= Information Verification =
== Information Verification ==
The following CAs are in the Information Gathering and Verification Phase as described in [[CA:How_to_apply]]. These requests need to complete the Information Gathering and Verification Phase before they can be put into the queue for public discussion.  
 
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'''.


<bugzilla>
<bugzilla>
Line 34: Line 32:
</bugzilla>
</bugzilla>


= Information Verification on Hold (Super CA) =
== 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'''.


<bugzilla>
<bugzilla>
Line 46: Line 46:
</bugzilla>
</bugzilla>


= Ready for Public Discussion =
== Ready for Public Discussion ==
Queue for discussion:
 
* Click on the "Whiteboard" column to sort
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'''.
** 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.


<bugzilla>
<bugzilla>
Line 66: Line 60:
</bugzilla>
</bugzilla>


= In Public Discussion =
== In Public Discussion ==
 
This section lists CAs whose inclusion is currently being publicly discussed. Action needed by: '''Public and CA'''.


<bugzilla>
<bugzilla>
Line 78: Line 74:
</bugzilla>
</bugzilla>


= Discussions On Hold =
== Discussions On Hold ==
The following list shows the CA inclusion/update requests that are in public discussion, but are waiting for the CA to provide additional or updated information that was asked for during the discussion, such as updating or translating the CP/CPS, or completing a more current or full audit. The discussion may continue as soon as the CA provides the additional or updated information.  
 
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'''.


<bugzilla>
<bugzilla>
Line 91: Line 88:
</bugzilla>
</bugzilla>


= Pending Approval =
== 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'''.


<bugzilla>
<bugzilla>
Line 103: Line 102:
</bugzilla>
</bugzilla>


= Approved and Pending Code Changes =
== 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'''.


<bugzilla>
<bugzilla>
Line 114: Line 115:
     }
     }
</bugzilla>
</bugzilla>
= Included CAs =
Spreadsheet of all included root certificates:
* https://wiki.mozilla.org/CA:IncludedCAs
= Roots Being Removed =
Upcoming Root Cert Removals:
* https://mozillacaprogram.secure.force.com/CA/UpcomingRootRemovalsReport
Certs that have been Removed:
* https://wiki.mozilla.org/CA:RemovedCAcerts
Gerv
Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1170293"

Navigation menu