New issue
Advanced search Search tips

Issue 807460 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 806905
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Site Isolation missing site whitelist capability

Reported by jngib...@gibert-fam.com, Jan 30 2018

Issue description

Version of Google Chrome (Wrench-> About Google Chrome): Version 63.0.3239.132 (Official Build) (64-bit)
Version of MSI (if applicable): 
Using group policy settings? Yes

The Site Isolation feature only allows the equivalent of Blacklisting a list of sites and placing them into Site Isolation; we need the ability to Whitelist trusted domains and force all other domains to use Site Isolation.
 

Comment 1 by nasko@chromium.org, Jan 30 2018

Cc: creis@chromium.org pastarmovj@chromium.org alex...@chromium.org
Components: Internals>Sandbox>SiteIsolation

Comment 2 by creis@chromium.org, Jan 30 2018

Mergedinto: 806905
Status: Duplicate (was: Unconfirmed)
Thanks for the report.  The primary use of the IsolateOrigins policy is to list the trusted, sensitive sites that need isolation from the rest of the web.  That's generally more effective than trying to isolate everything else and omitting the trusted site.

With that said, we're discussing whether an exception mechanism is meaningful or something that can be supported in  issue 806905 .

Sign in to add a comment