- go to
about:config - set
javascript.options.wasmtotrueorfalseto enable or disable webassembly
Instead of doing this it would just be more straightforward to just enable the resist fingerprinting flag.
https://support.mozilla.org/en-US/kb/firefox-protection-against-fingerprinting
Note that you will encounter broken websites
why would you want to do that though
Webassembly introduces security risks. I’m no pro at this and can’t explain it in more detail. But mull (firefox fork) has it disabled by default and some sites will break because there’s no webassembly.
Could you elaborate? Judging from the project’s page, it seems that they take security into mind too https://webassembly.org/docs/security/
I cna’t elaborate but I can point you forward
Here are the arkenfox settings https://arkenfox.github.io/gui/?s=wasm arkenfox disables webassembly. Look for javascript.options.wasm .
Following is the description there
Vulnerabilities [1] have increasingly been found, including those known and fixed
- in native programs years ago [2]. WASM has powerful low-level access, making
- certain attacks (brute-force) and vulnerabilities more possible
- [STATS] ~0.2% of websites, about half of which are for crytopmining / malvertising [2][3]
- [1] https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=wasm
- [2] https://spectrum.ieee.org/tech-talk/telecom/security/more-worries-over-the-security-of-web-assembly
- [3] https://www.zdnet.com/article/half-of-the-websites-using-webassembly-use-it-for-malicious-purposes
More discussions might be found on sites discussing Tor
