Security/Safe Browsing/V4 Implementation: Difference between revisions

Jump to navigation Jump to search
→‎Deliverables: add an explanation for why the variable length prefixes might cause problems
(→‎Deliverables: add an explanation for why the variable length prefixes might cause problems)
Line 51: Line 51:
# Check v4 prefixes (in addition to v4) but ignore the result
# 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)
# 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
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead


=== Bugs ===
=== Bugs ===
Confirmed users
908

edits

Navigation menu