Security/Download Protection: Difference between revisions

→‎Engineering: Create a separate section for the upstream file extension list
(→‎Engineering: mention the upstream source of file extensions)
(→‎Engineering: Create a separate section for the upstream file extension list)
Line 30: Line 30:
Most of the code lives in <tt>toolkit/components/downloads/ApplicationReputation.cpp</tt>.
Most of the code lives in <tt>toolkit/components/downloads/ApplicationReputation.cpp</tt>.


The list of file extensions that Chrome submits for remote verification lives inside a "File Type Policies" Chrome extension (see `chrome://components`) and uses this protobuf file as the source: https://cs.chromium.org/chromium/src/chrome/browser/resources/safe_browsing/download_file_types.asciipb
Upstream list of file extensions:
* Shipped to Chrome via a "File Type Policies" Chrome extension (see <tt>chrome://components</tt>)
* [https://github.com/fmarier/safebrowsing-tools/blob/master/parse-filetypes.py Binary protobuf extractor]
* [https://cs.chromium.org/chromium/src/chrome/browser/resources/safe_browsing/download_file_types.asciipb Source protobuf]


== QA ==
== QA ==
Confirmed users
908

edits