Following on from my previous post [1], I have now landed a patch that makes the Windows content process sandbox low integrity by default. (pref: security.sandbox.content.level=1)
I know of only one regression that this causes at the moment. This is that printing using the "Microsoft XPS Document Writer" or selecting "Print to file" fails (Bug 1156742). Due to this problem, this is a Nightly only change at the moment and will not currently move to Aurora when e10s does. If you need this feature, you could temporarily open a non-e10s window and print from there. If you use it a lot, then you can go back to the previous default (pref: security.sandbox.content.level=0), which requires a restart. For any other issues caused by this, please file them to block bug 1151767. I know this is stating the obvious :-), but you can test that they are caused by this change by retrying with the previous level 0 default as mentioned above. (Repeated from my previous post) You can turn on limited sandbox logging to the browser console with the pref: security.sandbox.windows.log This doesn't log all the things that the sandbox might block, but it should log things that we might be able to fix by adding new policy rules. You can filter the output with "Process Sandbox". Please copy (or attach) anything that looks like it might be relevant into the bug. You can also get a stack trace in the log entry with: security.sandbox.windows.log.stackTraceDepth The logging requires a restart, but changing the stack trace depth should not. Thanks, Bob [1] https://groups.google.com/forum/#!topic/mozilla.dev.platform/QaSdtSMGM7c _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
