Browse Protection
When safe browsing is set to available, the contents of all URL addresses need to be checked before being loaded. The URL address will be checked through two lists of malicious URLs and phishing URLs. Finally, based on the URL check the list, we will display the corresponding warning message on the Gap page.
Resource Handling
Whenever a resource is requested, the resource-distributing host creates a chained resource handler. This controls all events for the resource load process, and each processor can choose to cancel, pause, and resume the request. The secure Browse resource processor prevents the start of the chained processor, so it is the first to decide whether to allow this resource to be loaded. If safe browsing is forbidden, then the Safe Browsing resource processor will not be added directly to the chained processor, and there will be no safe browsing related actions.
Safe Browsing Gap page
When a resource is marked as a non-secure resource, the request for Jiangbei pauses and the Gap page is displayed. At this point, the user can choose to continue to download, or cancel the download, return to the front page. Malware Detail Collection
If the gap page and malware are related and then the page is HTTP instead of HTTPS, then tab is not an anonymous window, there will be an option to opt in to decide whether to send details about the dangerous resource for later analysis.
When the close Gap page is used, if the ComboBox is ticked, each additional detail will be collected asynchronously on the browser side. First, the browser history trace service redirects all relevant URLs, then requests the cache to get the headers of the relevant requests for those URLs, and finally sends the report out.
Download Protection
URL Verification
The download verification will be similar to browsing, although there will be some changes due to the download feature. The resource request header is received before the resource can be known, so searching for a friend download will go through the verification of browsing. The redirect list is saved in the URL request object, and once the download is started, all URLs are checked synchronously. Since the download is less latent and sensitive than the page load, we will also assign the memory database and the hash result cache. Finally, the verification will be synchronized with the download, except that the file name is zero until after the download and proofreading are complete.
If it is marked as malicious after the download is complete, the download bar will be replaced by a warning and discard button. If the user chooses to give up, the request will be canceled, otherwise it will be renamed to the real name.
Hash Verification
While downloading the file, we calculate the hash value of the file. Once the file has been downloaded, the hash value will be compared in the download proofing list. So far, we are only evaluating the usefulness of hash verification, so what is the UT show.
Client Phishing Detection
Client phishing detection, that is, if our current access page is not in the Safe browsing list, run a detection module in the current page. When the browser starts, the client-side detection service Gets the update model periodically afterwards. This model is sent to each rendering process through process communication and then delegated to and rendered view-related phishing classification agents. This also allows the classification to be processed in the rendering process.
Resource Request Process
The following is a process for a resource download request. Some of the details have been truncated to keep the size of the map appropriate. The Green line represents the usual scenario for loading a non-malware page, which simply requires a synchronized memory safe browsing database detection. A dashed line represents an asynchronous call. A magenta dot indicates a request to launch to the Google Safe Browsing service.
Note: Some small portions expire, especially when downloading related minor details. Chromium download code is currently being rewritten.
Metric
Safe browsing histogram using "SB2." Prefix. And the old version uses "SB.". There are also some safe browsing user metrics in filtering "SB"
Safe Browsing Database
It is the responsibility of the Secure browsing service to update each database that is safely browsed.
TODO (Matte): Provides more details about the database format and the update process.
Chrome Security Browser Implementation
