[Chrome ELF] Early browser security support.

chrome_elf/chrome_elf_util.cc

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome_elf/chrome_elf_util.h"
 
 #include <assert.h>
+#include <stddef.h>
 #include <windows.h>
-#include <stddef.h>
+#include <versionhelpers.h>  // windows.h must be before.
 
 #include "base/macros.h"
 #include "base/strings/string16.h"
 
 ProcessType g_process_type = ProcessType::UNINITIALIZED;
 
 namespace {
 
 const wchar_t kRegPathClientState[] = L"Software\\Google\\Update\\ClientState";
 const wchar_t kRegPathClientStateMedium[] =
@@ skipping 195 matching lines @@
     return;
   }
 
   g_process_type = ProcessType::BROWSER_PROCESS;
 }
 
 bool IsNonBrowserProcess() {
   assert(g_process_type != ProcessType::UNINITIALIZED);
   return g_process_type == ProcessType::NON_BROWSER_PROCESS;
 }
+
+typedef decltype(SetProcessMitigationPolicy)* SetProcessMitigationPolicyFunc;
+
+void EarlyBrowserSecurity() {
+  // This function is called from within DllMain.
+  // Don't do anything naughty while we have the loader lock.
+  if (::IsWindows8OrGreater()) {
+    SetProcessMitigationPolicyFunc set_process_mitigation_policy =
+        reinterpret_cast<SetProcessMitigationPolicyFunc>(::GetProcAddress(
+            ::GetModuleHandleW(L"kernel32.dll"), "SetProcessMitigationPolicy"));
+    if (set_process_mitigation_policy) {
+      // Disable extension DLLs in this process.
+      // (Legacy hooking.)
+      PROCESS_MITIGATION_EXTENSION_POINT_DISABLE_POLICY policy = {};
+      policy.DisableExtensionPoints = true;
+
+      if (!set_process_mitigation_policy(ProcessExtensionPointDisablePolicy,
+                                         &policy, sizeof(policy)))

[robertshield, 2016/02/01 22:40:50]

It would be nice to UMA this. 

Two ways come to mind - expose it to Chrome startup a la blacklist
(https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/chr...)
or run the check you have in the unit test for whether the mitigation policy is
enabled sometime during Chrome startup.

What do you think?

+        __debugbreak();
+    }
+  }
+  return;
+}