Extracting page shingle hashes for similarity detection.

chrome/common/safe_browsing/csd.proto

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 //
 // Client side phishing and malware detection request and response
 // protocol buffers.  Those protocol messages should be kept in sync
 // with the server implementation.
 //
 // If you want to change this protocol definition or you have questions
 // regarding its format please contact chrome-anti-phishing@googlegroups.com.
@@ skipping 50 matching lines @@
   // List of features that are extracted in the client but are not used in the
   // machine learning model.
   repeated Feature non_model_feature_map = 8;
 
   // The referrer URL.  This field might not be set, for example, in the case
   // where the referrer uses HTTPs.
   // OBSOLETE: Use feature 'Referrer=<referrer>' instead.
   optional string OBSOLETE_referrer_url = 9;
 
   // Field 11 is only used on the server.
+
+  // List of shingle hashes we extracted.
+  repeated uint32 shingle_hashes = 12 [packed = true];
 }
 
 message ClientPhishingResponse {
   required bool phishy = 1;
 
   // A list of SafeBrowsing host-suffix / path-prefix expressions that
   // are whitelisted.  The client must match the current top-level URL
   // against these whitelisted expressions and only apply a positive
   // phishing verdict above if the URL does not match any expression
   // on this whitelist.  The client must not cache these whitelisted
@@ skipping 243 matching lines @@
     // The upload was unsuccessful and the response is incomplete.
     UPLOAD_FAILURE = 1;
   }
 
   // Holds the upload status
   optional UploadStatus status = 1;
 
   // Holds the permalink where the results of scanning the binary are available
   optional string permalink = 2;
 }