New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 690008 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug

Blocking:
issue 690166



Sign in to add a comment

[Win] Chrome needs a third party module black/whitelist mechanism

Project Member Reported by chrisha@chromium.org, Feb 8 2017

Issue description

As part of blocking third party modules we will move to a "warning" phase, where the presence of blacklisted modules cause a warning dialog. When we move to blocking mode, we need a whitelist to allow certain modules (accessibility) in to the process. This list needs to be able to be updated asynchronously from Chrome updates, allowing quick in the field updates.
 
Design doc here (sorry, Google internal only):

https://docs.google.com/document/d/12Q7309-LMNB8ctxOi8t_Tn_40jEk5ghTJ9pDJ1Ua4D4/edit#
Blocking: 690166
The infrastructure for building the whitelist is currently up and running internally. Now focusing on the distribution mechanism.
Project Member

Comment 4 by bugdroid1@chromium.org, Sep 5 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b44337fcd33ea1fed107538ffab8e93dc53264fe

commit b44337fcd33ea1fed107538ffab8e93dc53264fe
Author: Chris Hamilton <chrisha@chromium.org>
Date: Tue Sep 05 18:23:36 2017

Create ThirdPartyModuleListComponentInstaller.

This creates a component installer for the third party module list
component. It also creates a corresponding ModuleListManager in
chrome/browser/conflicts for caching where the most recent module
list is stored on disk. This is necessary so that the module list
will be available to chrome_elf and sandbox code.

BUG=690008

Change-Id: I5fdd0d3cf138fd78f25b5cd40c145e8c415a5c48
Reviewed-on: https://chromium-review.googlesource.com/626858
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Patrick Monette <pmonette@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#499683}
[modify] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/browser/BUILD.gn
[modify] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/browser/chrome_browser_main.cc
[add] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/browser/component_updater/third_party_module_list_component_installer_win.cc
[add] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/browser/component_updater/third_party_module_list_component_installer_win.h
[modify] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/browser/conflicts/module_database_win.cc
[modify] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/browser/conflicts/module_database_win.h
[add] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/browser/conflicts/module_list_manager_win.cc
[add] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/browser/conflicts/module_list_manager_win.h
[add] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/browser/conflicts/module_list_manager_win_unittest.cc
[modify] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/browser/conflicts/proto/module_list.proto
[modify] https://crrev.com/b44337fcd33ea1fed107538ffab8e93dc53264fe/chrome/test/BUILD.gn

Sign in to add a comment