Security/Safe Browsing/V4 Implementation: Difference between revisions
< Security | Safe Browsing
Jump to navigation
Jump to search
(→Bugs) |
(→Bugs) |
||
Line 14: | Line 14: | ||
"whiteboard": "#sbv4-m0", | "whiteboard": "#sbv4-m0", | ||
"include_fields": "id, summary, status, assigned_to,resolution,", | "include_fields": "id, summary, status, assigned_to,resolution,", | ||
"order": "bug_id" | "order": "bug_id" | ||
} | } | ||
</bugzilla> | </bugzilla> |
Revision as of 07:46, 18 July 2016
Milestones
M0 (2016/7/31)
Deliverables
- Send v4 update request on time
- Parse v4 update response but not store to disk
- Use v4 request backoff settings
- v2 will still be up and running
Bugs
13 Total; 0 Open (0%); 12 Resolved (92.31%); 1 Verified (7.69%);
M1 (2016/9/30)
Deliverables
- Store v4 tables to disk (including fixed and variable length prefixes)
- Store table states
- Split v4 tables to different directory per provider
Bugs
41 Total; 1 Open (2.44%); 37 Resolved (90.24%); 3 Verified (7.32%);
M2 (Right before Hawaii Workweek)
Deliverables
- Check v4 prefixes (in addition to v4) but ignore the result
- v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
- Be careful of the variable length prefixes
Bugs
ID | Summary | Status | Assigned to | Resolution | |
---|---|---|---|---|---|
1305484 | Store state in the file instead of preference | RESOLVED | Henry Chang [:hchang] | FIXED | No |
1305581 | Verify that V4 updates were applied correctly by computing a checksum on the final result | RESOLVED | Dimi Lee [:dimi] | FIXED | No |
1305780 | Implement the update fail scheme for v4 | RESOLVED | Dimi Lee [:dimi] | FIXED | No |
1310142 | Move backup databases and raw table update data to a "update wreck" directory | RESOLVED | Henry Chang [:hchang] | FIXED | No |
1312323 | Single encoded value (either prefix or removal index) is not handled well | RESOLVED | Henry Chang [:hchang] | FIXED | No |
5 Total; 0 Open (0%); 5 Resolved (100%); 0 Verified (0%);