Closed Bug 1490736 Opened 8 years ago Closed 4 years ago

Add telemetry to analyze CRLIte filter age at time of evaluation

Categories

(Core :: Security: PSM, enhancement, P2)

Product:
Core
Component:
Security: PSM
Version:
64 Branch
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox64 --- affected

People

(Reporter: jcj, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [crlite] [psm-backlog])

We should collect telemetry that says, at the time CRLite is used to analyze a certificate, how old/stale the filter is. This will be useful in analyzing what "stale" should mean, for the purposes of choosing whether to rely on the filters or fall back to other means (e.g., OCSP).
Priority: -- → P2

I don't think we need this anymore. As of Bug 1765012 we consider a CRLite filter to be stale after 10 days.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.