Closed
Bug 1533884
Opened 6 years ago
Closed 5 years ago
Add telemetry to measure file corrupted count detected by CRC32 and sanity check
Categories
(Toolkit :: Safe Browsing, task, P2)
Toolkit
Safe Browsing
Tracking
()
RESOLVED
INVALID
People
(Reporter: dimi, Unassigned)
References
Details
The SHA256 integrity check for prefix files is replaced by CRC32 in Bug 1353956 for performance. We also added a simple sanity check while loading the prefix file.
It is worth adding telemetry to see how those methods help us find a corrupted prefix file. One thing we want to know from the telemetry is if the sanity check is good enough to detect corrupted file, if it is, we can also remove CRC32 from loading/writing prefixes.
Reporter | ||
Updated•6 years ago
|
Assignee: nobody → dlee
Status: NEW → ASSIGNED
Reporter | ||
Updated•6 years ago
|
Priority: P2 → P1
Reporter | ||
Updated•6 years ago
|
Type: enhancement → task
Priority: P1 → P2
Reporter | ||
Comment 1•6 years ago
|
||
Not actively work on this
Assignee: dlee → nobody
Status: ASSIGNED → NEW
Reporter | ||
Comment 2•5 years ago
|
||
I don't think we need this anymore
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•