Knock out injected safe-browsing prefixes.
commitc344b84e781a18e49fbf9b147b010fe2be1a4dcd
authorshess@chromium.org <shess@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 7 May 2014 16:35:25 +0000 (7 16:35 +0000)
committershess@chromium.org <shess@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 7 May 2014 16:35:25 +0000 (7 16:35 +0000)
treee17855278106aa66b5fbd23d7dcf0318f079e071
parent43baecc3d9812cbd1e32b2632a98006c1c2a1396
Knock out injected safe-browsing prefixes.

The safe-browsing update code has long injected prefixes when a fullhash was
seen.  This causes incorrect behavior.  That case can be detected by observing
prefixes in the same chunk as fullhashes, which cannot be sent by the server.

BUG=361248
R=jar@chromium.org, mattm@chromium.org

Review URL: https://codereview.chromium.org/263833005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268815 0039d316-1c4b-4281-b951-d872f2087c98
chrome/browser/safe_browsing/prefix_set.h
chrome/browser/safe_browsing/safe_browsing_database.cc
chrome/browser/safe_browsing/safe_browsing_database_unittest.cc
chrome/browser/safe_browsing/safe_browsing_store.cc
chrome/browser/safe_browsing/safe_browsing_store_file_unittest.cc
chrome/browser/safe_browsing/safe_browsing_store_unittest.cc
tools/metrics/histograms/histograms.xml