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

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Feature


Sign in to add a comment

Meta bug: Enforce Site Isolation policy in the browser process

Project Member Reported by creis@chromium.org, Nov 18 2017

Issue description

Once some or all sites are given dedicated renderer processes (using --isolate-origins or --site-per-process, respectively), the browser process can enforce that only renderer processes locked to the correct site can access that site's data.

This covers data such as cookies, passwords, localStorage, permissions, and other types of stored data.  It also includes blocking other renderer processes from receiving documents from these sites (though not all network data, since images, scripts, CSS, etc are still allowed in any web renderer process).

This is an umbrella bug to track the work to add enforcements for these properties in the browser process, so that an exploited renderer cannot access such data.
 

Comment 1 by creis@chromium.org, Nov 18 2017

Blockedon: 268640

Comment 2 by creis@chromium.org, Nov 18 2017

Blockedon: 734722 764958 770239 759184 781922 779444 726178
Blocking: 467770

Comment 3 by nasko@chromium.org, Nov 30 2017

Blockedon: 787019

Comment 4 by creis@chromium.org, Dec 5 2017

Blockedon: 791841

Comment 5 by nasko@chromium.org, Dec 7 2017

Blockedon: 792945

Comment 6 by nasko@chromium.org, Dec 7 2017

Blockedon: 792836

Comment 7 by creis@chromium.org, Dec 7 2017

Blockedon: 515309

Comment 8 by nasko@chromium.org, Dec 11 2017

Blockedon: 793953
Blockedon: 796968
Blockedon: 803220
Blockedon: 803235
Blockedon: -803235
Blockedon: -803220
Blockedon: 832180
Blockedon: 812168
Blockedon: 846346

Comment 17 Deleted

Blockedon: 850999
Blockedon: 846339
Blockedon: 736308
Blockedon: 855171
Blockedon: 858972
Blockedon: 871827
Blockedon: 874515
Blockedon: -855171

Comment 26 by alex...@chromium.org, Sep 20 (3 days ago)

Blockedon: 886976

Comment 27 by alex...@chromium.org, Yesterday (35 hours ago)

Blockedon: 888001

Sign in to add a comment