Get desktop application:
View/edit binary Protocol Buffers messages
The following protocol buffer holds the feedback report gathered from the user regarding the download.
The type of feedback for this report.
The original download ping
Stores the information of the user who provided the feedback.
Unstructed comments provided by the user.
The original download response sent from the verdict server.
Used in:
The information of user who provided the feedback. This is going to be useful for handling appeals.
Used in:
Used in:
,The final URL of the download (after all redirects).
This is the length in bytes of the download payload.
This repeated field will store all the redirects as well as the final URLs for the top-level tab URL (i.e., the URL that triggered the download) as well as for the download URL itself.
This field will only be set if the binary is signed.
True if the download was user initiated.
Name of the file where the download would be stored if the download completes. E.g., "bla.exe".
Locale of the device, eg en, en_US.
A binary contained in an archive (e.g., a .zip archive).
Used in:
A trust chain of certificates. Each chain begins with the signing certificate of the binary, and ends with a self-signed certificate, typically from a trusted root CA. This structure is analogous to CERT_CHAIN_CONTEXT on Windows.
Used in:
A single link in the chain.
Used in:
DER-encoded X.509 representation of the certificate.
Fields 2 - 7 are only used on the server.
This message contains various binary digests of the download payload.
Used in:
, ,Starting with Chrome M19 we're also sending back pings for Chrome extensions that get downloaded by users.
Used in:
,Currently all .exe, .cab and .msi files.
.crx files.
.apk files.
.zip files containing one of the other executable types.
.dmg, .pkg, etc.
Used in:
, , ,Windows Portable Executable image headers.
Used in:
IMAGE_DOS_HEADER.
IMAGE_FILE_HEADER.
IMAGE_OPTIONAL_HEADER32. Present only for 32-bit PE images.
IMAGE_OPTIONAL_HEADER64. Present only for 64-bit PE images.
IMAGE_SECTION_HEADER.
Contents of the .edata section.
Used in:
IMAGE_DEBUG_DIRECTORY.
Used in:
This will only be set if the referrer is available and if the resource type is either TAB_URL or DOWNLOAD_URL.
Type of the resources stored below.
Used in:
The final URL of the download payload. The resource URL should correspond to the URL field above.
A redirect URL that was fetched before hitting the final DOWNLOAD_URL.
The final top-level URL of the tab that triggered the download.
A redirect URL thas was fetched before hitting the final TAB_URL.
Used in:
, , ,All of the certificate chains for the binary's signing certificate. If no chains are present, the binary is not signed. Multiple chains may be present if any certificate has multiple signers.
True if the signature was trusted on the client.
Used in:
An arbitrary token that should be sent along for further server requests.
Used in:
A human-readable string describing the nature of the warning. Only if verdict != SAFE. Localized based on request.locale.
A URL to get more information about this warning, if available.
Used in:
Download is considered safe.
Download is considered dangerous. Chrome should show a warning to the user.
Download is unknown. Chrome should display a less severe warning.
The download is potentially unwanted.
The download is from a dangerous host.
Used in:
,Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
(message has no fields)
Used in:
Used in:
Note: skip tag 5 because it was previously used.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
URL that the client visited. The CGI parameters are stripped by the client.
The referrer URL. This field might not be set, for example, in the case where the referrer uses HTTPS.
List of resource urls that match the malware IP list.
Used in:
Resource type, the int value is a direct cast from the Type enum of ResourceType class defined in //src/webkit/commom/resource_type.h
The confirmed blacklisted bad IP and its url, which will be shown in malware warning, if the blacklist verdict is true. This IP string could be either in IPv4 or IPv6 format, which is the same as the ones client sent to server.
URL that the client visited. The CGI parameters are stripped by the client.
A 5-byte SHA-256 hash prefix of the URL. Before hashing the URL is canonicalized, converted to a suffix-prefix expression and broadened (www prefix is removed and everything past the last '/' is stripped). Marked OBSOLETE because the URL is sent for all users, making the hash prefix unnecessary.
Score that was computed on the client. Value is between 0.0 and 1.0. The larger the value the more likely the url is phishing.
Is true if the features for this URL were classified as phishing. Currently, this will always be true for all client-phishing requests that are sent to the server.
List of features that were extracted. Those are the features that were sent to the scorer and which resulted in client_score being computed.
The version number of the model that was used to compute the client-score. Copied from ClientSideModel.version().
List of features that are extracted in the client but are not used in the machine learning model.
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.
List of shingle hashes we extracted.
Used in:
Feature name. E.g., 'PageHasForms'.
Feature value is always in the range [0.0, 1.0]. Boolean features have value 1.0.
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 expressions. This whitelist will be empty for the vast majority of the responses but might contain up to 100 entries in emergency situations. Marked OBSOLETE because the URL is sent for all users, so the server can do whitelist matching.
This is used to send back upload status to the client after upload completion
Holds the upload status
Holds the permalink where the results of scanning the binary are available
Used in:
The upload was successful and a complete response can be expected
The upload was unsuccessful and the response is incomplete.