Allow the MITIGATION_WIN32K_DISABLE process mitigation to be set in the renderer sandbox.

sandbox/win/src/process_mitigations.cc

Index: sandbox/win/src/process_mitigations.cc
diff --git a/sandbox/win/src/process_mitigations.cc b/sandbox/win/src/process_mitigations.cc
index 0775b2d5ff146295b8624510d172deb0efa20edd..4e275b2beb2886744a32225b421caa8da47dfdee 100644
--- a/sandbox/win/src/process_mitigations.cc
+++ b/sandbox/win/src/process_mitigations.cc
@@ -316,7 +316,6 @@ bool CanSetProcessMitigationsPostStartup(MitigationFlags flags) {
 bool CanSetProcessMitigationsPreStartup(MitigationFlags flags) {
   // These mitigations cannot be enabled prior to startup.
   return !(flags & (MITIGATION_STRICT_HANDLE_CHECKS |

[jschuh, 2014/05/16 20:28:12]

You'll need to update this test too:
https://code.google.com/p/chromium/codesearch#chromium/src/sandbox/win/src/pr...

Just remove the MITIGATION_WIN32K_DISABLE line in that file since it turns out
we weren't properly testing it anyway. I'll add coverage in later.

[ananta, 2014/05/16 21:12:18]

Done.

-                    MITIGATION_WIN32K_DISABLE |
                     MITIGATION_DLL_SEARCH_ORDER));
 }