Ignore full hash response for stores that the database isn't interested in. |
||
Issue descriptionV4GetHashProtocolManager::ParseHashResponse currently caches FullHashInfo objects for all valid list identifiers. This can be different from the lists that the database is currently checking. Caching FullHashInfos for lists that the database isn't tracking is wasteful since the V4LocalDatabaseManager would never ask for those FullHashInfo objects. Solution: If the list for which we received the response is not one that we are currently tracking, ignore that ListUpdateResponse.
,
Nov 10 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bfcde5d0640845a210555226cd7de95cb5bb63b4 commit bfcde5d0640845a210555226cd7de95cb5bb63b4 Author: vakh <vakh@chromium.org> Date: Thu Nov 10 01:44:15 2016 Ignore ThreatMatch responses for lists that we don't care about. Due to aliasing used on the server side, the server may send ThreatMatch response for lists that we don't track. For instance, ThreatMatch with platform_type as CHROME on Linux. Ignore such ThreatMatch responses. BUG= 663247 Review-Url: https://codereview.chromium.org/2490753002 Cr-Commit-Position: refs/heads/master@{#431131} [modify] https://crrev.com/bfcde5d0640845a210555226cd7de95cb5bb63b4/components/safe_browsing_db/v4_get_hash_protocol_manager.cc [modify] https://crrev.com/bfcde5d0640845a210555226cd7de95cb5bb63b4/components/safe_browsing_db/v4_get_hash_protocol_manager.h [modify] https://crrev.com/bfcde5d0640845a210555226cd7de95cb5bb63b4/components/safe_browsing_db/v4_get_hash_protocol_manager_unittest.cc
,
Nov 15 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by vakh@chromium.org
, Nov 8 2016