Closed
Bug 1490736
Opened 6 years ago
Closed 2 years ago
Add telemetry to analyze CRLIte filter age at time of evaluation
Categories
(Core :: Security: PSM, enhancement, P2)
Tracking
()
RESOLVED
WONTFIX
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
Comment 1•2 years ago
|
||
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: 2 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•