1// Copyright (c) 2010 The Chromium Authors. All rights reserved. 2// Use of this source code is governed by a BSD-style license that can be 3// found in the LICENSE file. 4// 5// Client side phishing and malware detection request and response 6// protocol buffers. Those protocol messages should be kept in sync 7// with the server implementation. 8// 9// If you want to change this protocol definition or you have questions 10// regarding its format please contact chrome-anti-phishing@googlegroups.com. 11 12syntax = "proto2"; 13 14option optimize_for = LITE_RUNTIME; 15 16package safe_browsing; 17 18message ClientPhishingRequest { 19 // URL that the client visited. The CGI parameters are stripped by the 20 // client. 21 required string url = 1; 22 23 // Score that was computed on the client. Value is between 0.0 and 1.0. 24 // The larger the value the more likely the url is phishing. 25 required float client_score = 2; 26 27 // Note: we're skipping tag 3 because it was previously used. 28 29 // Is true if the features for this URL were classified as phishing. 30 // Currently, this will always be true for all client-phishing requests 31 // that are sent to the server. 32 optional bool is_phishing = 4; 33 34 message Feature { 35 // Feature name. E.g., 'PageHasForms'. 36 required string name = 1; 37 38 // Feature value is always in the range [0.0, 1.0]. Boolean features 39 // have value 1.0. 40 required double value = 2; 41 } 42 43 // List of features that were extracted. Those are the features that were 44 // sent to the scorer and which resulted in client_score being computed. 45 repeated Feature feature_map = 5; 46} 47 48message ClientPhishingResponse { 49 required bool phishy = 1; 50} 51