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

I have disabled Web Assembly in my Chrome, but nothing changed #2

Open
detro opened this issue Mar 26, 2018 · 6 comments
Open

I have disabled Web Assembly in my Chrome, but nothing changed #2

detro opened this issue Mar 26, 2018 · 6 comments

Comments

@detro
Copy link

detro commented Mar 26, 2018

Chrome Version 65.0.3325.181 (Official Build) (64-bit)

screen shot 2018-03-26 at 16 11 05

I then tried different WASM application, especially coinhive.com and other ads-crypto-miners: they all still work just fine.

I'm trying to protect myself without the need of using AdBlock for it. But Chrome is making it really hard.

@tophf
Copy link

tophf commented Mar 28, 2018

This flag does not disable WebAssembly.
You need to run Chrome with --js-flags=--noexpose_wasm command line flag.
Look for tutorials on altering Chrome shortcut for your OS.

In Windows you might also want to modify the chrome's command line in registry:
HKEY_CLASSES_ROOT\ChromeHTML\shell\open\command
HKEY_CLASSES_ROOT\http\shell\open\command
HKEY_CLASSES_ROOT\https\shell\open\command
And then uncheck the write permission on these keys so that the changes persist on next auto-update of Chrome.

Note, many/all miners run a fallback code in pure js.

@stevespringett
Copy link
Owner

I tried --disable-features=WebAssembly,AsmJsToWebAssembly but it didn't work on Chrome 66 (macOS). --js-flags=--noexpose_wasm does work consistently for me though.

On macOS, we need to start Chrome using the following command:

open /Applications/Google\ Chrome.app --args --js-flags=--noexpose_wasm

It should be noted that the Brave browser (Laptop edition) is build on Chromium and Webassembly can be disabled by the same method, using --js-flags=--noexpose_wasm

@stevespringett
Copy link
Owner

@tophf thanks for the updates on chrome, specifically the command-line arg and the registry advise. I've added the content to the projects readme and acknowledged your contribution.

@detro
Copy link
Author

detro commented Jun 3, 2018

I will give it another go, but I checked all of the above and even got a bug about this o the Mac OS X version of Chrome open and assigned: https://bugs.chromium.org/p/chromium/issues/detail?id=825845

If this is now working as expected, it means in the meantime they fixed it.

@stevespringett
Copy link
Owner

Ah, very good background information @eladkarako . Thank you. If you find that the flags make it into Google Chrome before I do, please ping this ticket and update it if you could.

@basketdou
Copy link

basketdou commented Jul 22, 2021

Hello.
Version 91.0.4472.164 (Official Build) Arch Linux (64-bit)
I managed to turn off WebAssembly by disabling the following parameters in chrome://flags:

  • #enable-webassembly-baseline
  • #enable-webassembly-lazy-compilation
  • #enable-webassembly-simd
  • #enable-webassembly-threads
  • #enable-webassembly-tiering .

It seems that it is off now after launching this script from StackOverflow.
Option --js-flags=--noexpose_wasm didn't work for some reason.

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

No branches or pull requests

4 participants