| commit | 956e0caebaa1d3207d98821a442dfa0507d00757 | [log] [tgz] |
|---|---|---|
| author | Will Harris <[email protected]> | Fri Aug 23 20:47:39 2019 |
| committer | Commit Bot <[email protected]> | Fri Aug 23 20:47:39 2019 |
| tree | e41cbe5429b5b36acfb75fa01b5304d303366f4c | |
| parent | 312f5f1cac30780118dcd00333d4004d66676dae [diff] [blame] |
Add enterprise policy for renderer CIG. Whether to enable/disable is checked on the launcher thread in content. But the actual flag is only accessible on the main thread from chrome, so the plumbing in render_process_host and content_browser_client exists to wire these two together. BUG=750886 TEST=set policy, check renderers start without CIG. Change-Id: I2ea2286d9e244734abe15b9f8beb62b3f97ffd71 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758589 Commit-Queue: Will Harris <[email protected]> Reviewed-by: Lutz Justen <[email protected]> Reviewed-by: Avi Drissman <[email protected]> Reviewed-by: Owen Min <[email protected]> Cr-Commit-Position: refs/heads/master@{#690060}
diff --git a/chrome/browser/prefs/browser_prefs.cc b/chrome/browser/prefs/browser_prefs.cc index 6972248..27a0a9a 100644 --- a/chrome/browser/prefs/browser_prefs.cc +++ b/chrome/browser/prefs/browser_prefs.cc
@@ -697,6 +697,7 @@ #endif #if defined(OS_WIN) + registry->RegisterBooleanPref(prefs::kRendererCodeIntegrityEnabled, true); component_updater::RegisterPrefsForSwReporter(registry); #if BUILDFLAG(GOOGLE_CHROME_BRANDING) IncompatibleApplicationsUpdater::RegisterLocalStatePrefs(registry);