Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable strict site isolation by default #603

Closed
jumde opened this issue Jul 19, 2018 · 5 comments
Closed

Enable strict site isolation by default #603

jumde opened this issue Jul 19, 2018 · 5 comments

Comments

@jumde
Copy link
Contributor

jumde commented Jul 19, 2018

brave/browser-laptop#14766

@bbondy bbondy added this to the Releasable builds milestone Jul 26, 2018
@bbondy
Copy link
Member

bbondy commented Jul 26, 2018

We have this enabled by default now with C68

@bbondy bbondy closed this as completed Jul 26, 2018
@diracdeltas
Copy link
Member

@bbondy it shows up still as disabled in chrome://flags/#enable-site-per-process
screen shot 2018-07-30 at 8 36 34 pm

tested on MacOS Version 0.53.0 Chromium: 68.0.3440.68 (Official Build) dev (64-bit)

@bbondy bbondy reopened this Jul 31, 2018
@bbondy
Copy link
Member

bbondy commented Jul 31, 2018

Per the steps here:
https://www.chromium.org/Home/chromium-security/site-isolation#TOC-Verifying

I believe it's enabled. I think the chrome://flags setting is no longer used.
You can also see a quick recap on chrome://process-internals which shows it working.
I verified with Chrome's task manager with the test case they describe above though and it seems to be working correctly.

Let me know if I'm missing something or not though, it wouldn't be hard to also enable that flag. But I think the UI for the flag will be removed in an upcoming Chromium version. Unless I'm not understanding that the flag does something extra. Please lmk @diracdeltas. Thanks for checking!

@bbondy bbondy closed this as completed Jul 31, 2018
@diracdeltas
Copy link
Member

diracdeltas commented Aug 13, 2018

if the listed test plan works, closing this sgtm.

if there is a more general issue that chrome://flags in brave doesn't reflect reality, we should either fix that or at least put a disclaimer on chrome://flags.

@btlechowski
Copy link

btlechowski commented Sep 24, 2018

Verification passes on

Brave 0.55.6 Chromium: 70.0.3538.16 (Official Build) dev (64-bit)
Revision 16ed95b41bb05e565b11fb66ac33c660b721f778-refs/branch-heads/3538@{#306}
OS Windows 7

Checked chrome://process-internals and test case from https://www.chromium.org/Home/chromium-security/site-isolation#TOC-Verifying

Verification passes on

Brave 0.55.6 Chromium: 70.0.3538.16 (Official Build) dev (64-bit)
Revision 16ed95b41bb05e565b11fb66ac33c660b721f778-refs/branch-heads/3538@{#306}
OS Linux

Verified passed with

Brave 0.55.10 Chromium: 70.0.3538.22 (Official Build) beta(64-bit)
Revision ac9418ba9c3bd7f6baaffa0b055dfe147e0f8364-refs/branch-heads/3538@{#468}
OS Mac OS X

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants