-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Disable SharedArrayBuffer #1051
Milestone
Comments
11 tasks
Verification Pass with
Verification Passed on
Verification Passed on
|
mkarolin
added a commit
to brave/brave-core
that referenced
this issue
Mar 12, 2019
This change is due to failure of browser test SharedArrayBufferDisabledTest.IsDisabled. Needs security review. In C73 this feature was disabled by default. In C74 it is enabled by default on all platforms but Android. When enabled, this feature also enables SharedArrayBuffer feature, which we have disabled due to vulnerability to Spectre. See brave/brave-browser#1051. Chromium change: commit f9cc6b912e601070728b449892097cec0d59cbfa Author: Ben Smith <binji@chromium.org> Date: Wed Feb 27 02:09:43 2019 +0000 [wasm] Enable wasm threads by default See intent to ship blink-dev thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/tD6np-OG2PU Bug: chromium:754910
mkarolin
added a commit
to brave/brave-core
that referenced
this issue
Mar 15, 2019
This change is due to failure of browser test SharedArrayBufferDisabledTest.IsDisabled. Needs security review. In C73 this feature was disabled by default. In C74 it is enabled by default on all platforms but Android. When enabled, this feature also enables SharedArrayBuffer feature, which we have disabled due to vulnerability to Spectre. See brave/brave-browser#1051. Chromium change: commit f9cc6b912e601070728b449892097cec0d59cbfa Author: Ben Smith <binji@chromium.org> Date: Wed Feb 27 02:09:43 2019 +0000 [wasm] Enable wasm threads by default See intent to ship blink-dev thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/tD6np-OG2PU Bug: chromium:754910
mkarolin
added a commit
to brave/brave-core
that referenced
this issue
Mar 18, 2019
This change is due to failure of browser test SharedArrayBufferDisabledTest.IsDisabled. Needs security review. In C73 this feature was disabled by default. In C74 it is enabled by default on all platforms but Android. When enabled, this feature also enables SharedArrayBuffer feature, which we have disabled due to vulnerability to Spectre. See brave/brave-browser#1051. Chromium change: commit f9cc6b912e601070728b449892097cec0d59cbfa Author: Ben Smith <binji@chromium.org> Date: Wed Feb 27 02:09:43 2019 +0000 [wasm] Enable wasm threads by default See intent to ship blink-dev thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/tD6np-OG2PU Bug: chromium:754910
mkarolin
added a commit
to brave/brave-core
that referenced
this issue
Mar 19, 2019
This feature was disabled by brave/brave-browser#1051 to mitigate Spectre. Spectre was later addressed by Chromium via site isolation and Chromium re-enabled SharedArrayBuffer, but Brave didn't. Now in C74, WebAssemblyThreads feature is being enabled by default. Since WebAssemblyThreads is built with and auto-enables SharedArrayBuffer, there is no reason for us to continue keeping SharedArrayBuffer disabled. Aslo, removed a browser test for checking that SharedArrayBuffer is disabled. Chromium change making WebAssemblyThreads enabled by default: commit f9cc6b912e601070728b449892097cec0d59cbfa Author: Ben Smith <binji@chromium.org> Date: Wed Feb 27 02:09:43 2019 +0000 [wasm] Enable wasm threads by default See intent to ship blink-dev thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/tD6np-OG2PU Bug: chromium:754910
mkarolin
added a commit
to brave/brave-core
that referenced
this issue
Mar 20, 2019
This feature was disabled by brave/brave-browser#1051 to mitigate Spectre. Spectre was later addressed by Chromium via site isolation and Chromium re-enabled SharedArrayBuffer, but Brave didn't. Now in C74, WebAssemblyThreads feature is being enabled by default. Since WebAssemblyThreads is built with and auto-enables SharedArrayBuffer, there is no reason for us to continue keeping SharedArrayBuffer disabled. Aslo, removed a browser test for checking that SharedArrayBuffer is disabled. Chromium change making WebAssemblyThreads enabled by default: commit f9cc6b912e601070728b449892097cec0d59cbfa Author: Ben Smith <binji@chromium.org> Date: Wed Feb 27 02:09:43 2019 +0000 [wasm] Enable wasm threads by default See intent to ship blink-dev thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/tD6np-OG2PU Bug: chromium:754910
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Details here: brave/browser-laptop#12570
STR:
The text was updated successfully, but these errors were encountered: