Thanks Chris, Yeah, I've only had a small hand in this. As well as tabraldes, of course, I must mention bbondy, aklotz, imelven and probably several others of which I'm unaware or can't think of right now (sorry). Not to mention everyone who's worked to get e10s this far.
Cheers, Bob ----- Original Message ----- > From: "Chris Peterson" <cpeter...@mozilla.com> > To: dev-platform@lists.mozilla.org > Sent: Monday, 1 December, 2014 8:08:37 AM > Subject: Re: A first step for content process sandboxing on Windows. > > Awesome, Bob and tabraldes! Firefox sandboxing on Windows is real. :) > > chris > > > On 11/29/14 2:03 PM, Bob Owen wrote: > > Hi everyone, > > > > Patches have just landed on mozilla-inbound to turn on the content process > > sandbox on Windows by default. > > This means that anyone running on Windows with e10s enabled, will also be > > using the Chromium sandbox. > > > > The policy is only weak at the moment, to try and ensure that it doesn't > > break anything. > > So, the only thing it sets is a USER_NON_ADMIN restricted access token. > > > > You can run with a more strict version of the policy by setting the pref: > > security.sandbox.windows.content.moreStrict=true > > > > This will require a restart. > > Many things should still work with this policy. > > Although some things will hang or crash, in particular pages that play > > media. > > > > If you have any questions you can find me in #boxing or possibly in person > > next week! > > > > Cheers, > > Bob > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
