CA/Incident Dashboard: Difference between revisions

From MozillaWiki
< CA
Jump to navigation Jump to search
(Add dashboard for historic bugs as well)
(Moved Closed bugs section to separate wiki page)
Line 46: Line 46:
= Closed CA Bugs =
= Closed CA Bugs =
== Closed CA Compliance Bugs ==
== Closed CA Compliance Bugs ==
A historical view of past CA compliance bugs. These bugs may have been valid and remedied by the CA, or may have been deemed invalid and closed as unnecessary.
A historical view of past CA compliance bugs may be found here:
 
* https://wiki.mozilla.org/CA/Closed_Incidents
<bugzilla>
    {
        "component":"CA Certificate Mis-Issuance",
        "status":["CLOSED", "RESOLVED", "VERIFIED"],
        "whiteboard":"compliance",
        "cf_blocking_b2g_type":"contains",
        "include_fields": ["id", "summary", "status", "resolution", "last_change_time"]
    }
</bugzilla>

Revision as of 23:34, 5 April 2018

Open CA Bugs in Bugzilla

Open Incident Related Bugs

Investigation or Discussion

Concern has been raised about certificates that a CA has issued. Investigation and/or discussion in progress.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Resulting CA Action Items

The concern about a CA's certificates has been confirmed, and the CA has follow-up action items.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Open CA Compliance Bugs

A CA compliance bug relates to a concern about a CA's certificates failing to comply with Mozilla's CA Certificate Policy and/or the CA/Browser Forum's Baseline Requirements, and is determined to not be an imminent security concern.

Anyone may create a CA Compliance bug as follows:

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Closed CA Bugs

Closed CA Compliance Bugs

A historical view of past CA compliance bugs may be found here: