Adding a new delayed analysis that verify binaries signature.

chrome/browser/browser_process_impl.cc

Index: chrome/browser/browser_process_impl.cc
diff --git a/chrome/browser/browser_process_impl.cc b/chrome/browser/browser_process_impl.cc
index 01cac71b8f0858ec7963941690669f68e81170d2..0ecf35308ded5889b401f31692d394168e05b114 100644
--- a/chrome/browser/browser_process_impl.cc
+++ b/chrome/browser/browser_process_impl.cc
@@ -61,6 +61,7 @@
 #include "chrome/browser/printing/print_preview_dialog_controller.h"
 #include "chrome/browser/profiles/profile_manager.h"
 #include "chrome/browser/renderer_host/chrome_resource_dispatcher_host_delegate.h"
+#include "chrome/browser/safe_browsing/binary_integrity_service.h"
 #include "chrome/browser/safe_browsing/safe_browsing_service.h"
 #include "chrome/browser/shell_integration.h"
 #include "chrome/browser/status_icons/status_tray.h"
@@ -1042,6 +1043,9 @@ void BrowserProcessImpl::PreMainMessageLoopRun() {
   storage_monitor::StorageMonitor::Create();
 #endif
 
+  // Register a delayed analysis for binary integrity.
+  safe_browsing::RegisterBinaryIntegrityAnalysis();

[mattm, 2014/08/07 20:16:01]

Agree about avoiding adding more stuff here, maybe it can just be put in
SafeBrowsingService::Initialize, or the CreateSafeBrowsingService function?

(may also need some #if defined(FULL_SAFE_BROWSING) check depending where it
goes)

[pmonette_google.com, 2014/08/07 21:29:28]

Okay I've added a function to register all the delayed analysis in
safe_browsing_service.cc. Let me know what you think.

I don't think the FULL_SAFE_BROWSING check is needed yet. There has been some
discussion about adding more thorough checks for full safe-browsing enabled
profiles sometime in the future though.

I also think that we thought about reporting more information in the reports if
full safe-browsing is enabled but if this ever happens, the incident reporting
service will take care of that.

[grt (UTC plus 2), 2014/08/08 02:23:05]

I think you're thinking of extended safe browsing rather than
FULL_SAFE_BROWSING. The former is a user-controlled setting in the browser,
while the latter is a build-time switch that turns on/off various safe browsing
features. The incident reporting service and all related code is
FULL_SAFE_BROWSING only.

[pmonette_google.com, 2014/08/08 15:05:42]

Oh this is confusing. Thanks!

+
   platform_part_->PreMainMessageLoopRun();
 }