Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(148)

Issue 232223005: Knock out injected safe-browsing prefixes. (Closed)

Created:
6 years, 8 months ago by Scott Hess - ex-Googler
Modified:
6 years, 7 months ago
Reviewers:
mattm
CC:
chromium-reviews, jar (doing other things), asvitkine+watch_chromium.org
Visibility:
Public.

Description

[Superceeded by https://codereview.chromium.org/263833005/ ] 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

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+224 lines, -7 lines) Patch
M chrome/browser/safe_browsing/safe_browsing_database.cc View 4 chunks +63 lines, -7 lines 0 comments Download
M chrome/browser/safe_browsing/safe_browsing_database_unittest.cc View 2 chunks +99 lines, -0 lines 0 comments Download
M chrome/browser/safe_browsing/safe_browsing_store.cc View 3 chunks +55 lines, -0 lines 0 comments Download
M tools/metrics/histograms/histograms.xml View 1 chunk +7 lines, -0 lines 0 comments Download

Messages

Total messages: 2 (0 generated)
Scott Hess - ex-Googler
Apologies for the delay - I had it all ready to go, then thought "Maybe ...
6 years, 8 months ago (2014-04-10 00:17:01 UTC) #1
mattm
6 years, 8 months ago (2014-04-10 02:02:41 UTC) #2
This LGTM, but did you see my question about crbug.com/172527 on the email
thread? Doesn't this change increase the impact of that issue?

Powered by Google App Engine
This is Rietveld 408576698