Security/Safe Browsing/V4 Implementation: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "= 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 #...")
 
Line 9: Line 9:


=== Bugs ===
=== Bugs ===
<bugzilla>
  {
    "whiteboard": "#sbv4-m0",
    "include_fields": "id, summary, status, assigned_to,resolution,",
    "order": "bug_id"
  }
</bugzilla>


== M1 (2016/9/30) ==
== M1 (2016/9/30) ==

Revision as of 07:39, 18 July 2016

Milestones

M0 (2016/7/31)

Deliverables

  1. Send v4 update request on time
  2. Parse v4 update response but not store to disk
  3. Use v4 request backoff settings
  4. v2 will still be up and running

Bugs

Full Query
ID Summary Status Assigned to Resolution
1254766 Stop caching Safe Browsing completions to disk RESOLVED Dimi Lee [:dimi] FIXED No
1264885 Refactor the listmanager to add support for both V2 an V4 of the protocol RESOLVED Henry Chang [:hchang] FIXED No
1272239 Support completion for test database RESOLVED Dimi Lee [:dimi] FIXED No
1273398 Implement RequestBackoff for Safe Browsing v4 RESOLVED Henry Chang [:hchang] FIXED No
1273410 "Table Name" (used by v2) to "Threat Type" conversion RESOLVED INVALID No
1273412 "Table/List name" (v2) to "Threat type" (v4) conversion RESOLVED Henry Chang [:hchang] DUPLICATE No
1274112 Implement Safe Browsing v4 update request VERIFIED Henry Chang [:hchang] FIXED No
1275507 XPCOM API to create SafeBrowsing v4 update request RESOLVED Henry Chang [:hchang] FIXED No
1276595 Parse SafeBrowsing v4 update response RESOLVED Henry Chang [:hchang] DUPLICATE No
1281083 Changing the urlclassifier.*Table prefs doesn't take effect before the next browser restart RESOLVED Dimi Lee [:dimi] FIXED No
1287059 Keep track of the Safe Browsing V4 state in one pref per table RESOLVED Henry Chang [:hchang] FIXED No
1305567 V4 updates always fail with a 400 status code RESOLVED Henry Chang [:hchang] FIXED No
1307541 V4 updates are not scheduled at the right time RESOLVED Henry Chang [:hchang] FIXED No

13 Total; 0 Open (0%); 12 Resolved (92.31%); 1 Verified (7.69%);


M1 (2016/9/30)

Deliverables

  1. Store v4 tables to disk (including fixed and variable length prefixes)
  2. Store table states
  3. Split v4 tables to different directory per provider

Bugs

M2 (Right before Hawaii Workweek)

Deliverables

  1. Check v4 prefixes (in addition to v4) but ignore the result
  2. v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
    1. Be careful of the variable length prefixes

Bugs

Retrieved from "https://wiki.mozilla.org/index.php?title=Security/Safe_Browsing/V4_Implementation&oldid=1140049"