Closed
Bug 1631847
Opened 4 years ago
Closed 4 years ago
use timestamp field from crlite entries instead of filename to determine most recent filters/stashes
Categories
(Core :: Security: PSM, task, P1)
Core
Security: PSM
Tracking
()
RESOLVED
FIXED
mozilla78
People
(Reporter: keeler, Assigned: keeler)
References
(Blocks 1 open bug)
Details
(Whiteboard: [psm-assigned])
Attachments
(1 file)
https://github.com/mozilla/crlite/issues/67 will be adding a timestamp field to crlite entries. The implementation should use this to determine the most recent filter/stash.
|
||
Comment 1•4 years ago
|
||
Proposed schema posted: https://github.com/mozilla/crlite/issues/67#issuecomment-622527143
|
|
||
Comment 2•4 years ago
|
||
|
Assignee | |
Updated•4 years ago
|
Severity: -- → N/A
status-firefox75:
--- → wontfix
status-firefox76:
--- → wontfix
status-firefox77:
--- → wontfix
status-firefox78:
--- → affected
status-firefox-esr68:
--- → wontfix
|
|
Assignee | |
Comment 3•4 years ago
|
||
Pushed by dkeeler@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3c6c825754a5 use effectiveTimestamp and parent fields from CRLite entries to determine most recent full and incremental filters r=jcj
|
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in
before you can comment on or make changes to this bug.
Description
•