Bug 1529954: Move ARM64 Windows content sandbox back to level 5. r=jimm
authorBob Owen <bobowencode@gmail.com>
Tue, 26 Feb 2019 10:39:48 +0000
changeset 461095 17ad931f439ce74288a8777400c40a19aa6971c6
parent 461094 7ad5d74c3240164caf11b5784958988294af05cc
child 461096 ea34ac7461b0419faf1ca5b23e611887d73d8172
push id112156
push userbobowencode@gmail.com
push dateTue, 26 Feb 2019 10:40:19 +0000
treeherdermozilla-inbound@17ad931f439c [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersjimm
bugs1529954
milestone67.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1529954: Move ARM64 Windows content sandbox back to level 5. r=jimm
browser/app/profile/firefox.js
--- a/browser/app/profile/firefox.js
+++ b/browser/app/profile/firefox.js
@@ -1004,21 +1004,17 @@ pref("dom.ipc.plugins.sandbox-level.flas
 #endif
 
 #if defined(MOZ_CONTENT_SANDBOX)
 // This controls the strength of the Windows content process sandbox for testing
 // purposes. This will require a restart.
 // On windows these levels are:
 // See - security/sandbox/win/src/sandboxbroker/sandboxBroker.cpp
 // SetSecurityLevelForContentProcess() for what the different settings mean.
-#if defined(_ARM64_)
-pref("security.sandbox.content.level", 2);
-#else
 pref("security.sandbox.content.level", 5);
-#endif
 
 // This controls the depth of stack trace that is logged when Windows sandbox
 // logging is turned on.  This is only currently available for the content
 // process because the only other sandbox (for GMP) has too strict a policy to
 // allow stack tracing.  This does not require a restart to take effect.
 pref("security.sandbox.windows.log.stackTraceDepth", 0);
 #endif