Confirmed users
238
edits
Security/Features/Application Reputation Design Doc: Difference between revisions
Jump to navigation
Jump to search
Security/Features/Application Reputation Design Doc (view source)
Revision as of 15:37, 23 July 2014
, 23 July 2014→Background
| Line 3: | Line 3: | ||
== Background == | == Background == | ||
Google has offered an application reputation feature to detect malicious downloads as part of Google Safe Browsing since 2012 [http://blog.chromium.org/2012/01/all-about-safe-browsing.html]. Although this part of the Safe Browsing API is not documented, they have offered it to us for use in Firefox. Malicious download detection is separate from detection of phishing and malware pages, though both features use some of the same mechanisms. | Google has offered an application reputation feature to detect malicious downloads as part of Google Safe Browsing since 2012 [http://blog.chromium.org/2012/01/all-about-safe-browsing.html]. Although this part of the Safe Browsing API is not documented, they have offered it to us for use in Firefox. Malicious download detection is separate from detection of phishing and malware pages (present in Firefox since 2.0), though both features use some of the same mechanisms. | ||
This document attempts to document all of the things that Google Chrome does, so that even in the absence of official API documentation from Google, we collectively have a better chance of implementing this feature correctly. | This document attempts to document all of the things that Google Chrome does, so that even in the absence of official API documentation from Google, we collectively have a better chance of implementing this feature correctly. | ||