4 ms·
This isn't going to work I suspect. Ad blockers work because ad companies are too lazy to make appliances/software to embed their ad packages as first party ent
by kodablah 9y ago
This isn't going to work I suspect. Ad blockers work because ad companies are too lazy to make appliances/software to embed their ad packages as first party entities. This is exacerbated by the need for third party cookie access. Utilizing client CPU for mining doesn't need that. They can simply embed the JS script (which presumably would have the WASM binary embedded) and go. At least that's how I would do it if I were nefarious. And I'd add significant randomness to prevent pattern matching, but ad blockers are stupid primitive css selector or URL matchers anyways.
- ape4 9y agoMining requires lots of Math.something() functions. Maybe they can set a max for that.
- tobyhinloopen 9y agoYou can use other implementations that not require Math.
- ape4 9y agoJust curious... like what?
- Momquist 9y agoI feel whitelisting JS is becoming the sanest approach, despite all its shortcomings.
- shostack 9y agoIs there anything comparable to NoScript that works in Firefox Quantum?
- Momquist 9y agouMatrix, although it doesn't have the various anti-XSS protections of NoScript. But its UI is great, much better than NS IMHO, and it's not limited to script blocking. https://github.com/gorhill/uMatrix https://github.com/gorhill/uMatrix
- gorhill 9y agoThe dev build support specifically blocking web workers, typically used by cryptominers. So at this point I think it will be a good idea to block web workers by default everywhere, and enable only if a trusted site needs them.
- KwanEsq 9y agoNoScript[1] works pretty well. [1] https://addons.mozilla.org/firefox/addon/noscript/ https://addons.mozilla.org/firefox/addon/noscript/
- shostack 9y agoHuh...for some reason I thought it was not compatible. Ugh, now the only thing holding me back from upgrading is some of my other addons. I hate having to wait forever to upgrade because I use some less popular addons with long update cycles.
- CannisterFlux 9y agoI ditched a load of addons for Firefox 57. Just embrace the change, find replacements, or move on and stop using them. It's hard, but I found I adapted quite quickly. For NoScript, even though it is now available, I switched to ublock in medium-mode since NS was delayed until a couple of weeks after 57 hit. Both ublock and NS now use the same Content-Security-Policy filtering approach (NoScript switched to CSP for the webextension release, ublock did it this way before) and so both now suffer from this bug that means noscript tags are not rendered/parsed at all https://github.com/gorhill/uBlock/issues/308 https://github.com/gorhill/uBlock/issues/308 - so I felt I may as well just use ublock. Full-on global-disallow NoScript with that bug makes many sites completely unusable since their graceful-degraded noscript blocks are not shown, and UI changes in the webextension release made it too fiddly to use IMO.
- shostack 9y agoIs there decent mouse gesture support for 57? That's one thing I'm not willing to budge on in terms of ditching old functionality from addons. Mouse gestures have become a way of life for me.
- CannisterFlux 9y agoYes, me too. This was more of a pain than NoScript, but after trying a few I switched to "Foxy Gestures" and I'm mostly happy with it. It has right-button+move-in-a-pattern gestures, as well as "chorded" right/left clicks and wheel gestures. It does have 2 issues - 1st it does not work on special pages due to security restrictions. This means stuff like about:blank, when a page fails to load, preferences pages, and Mozilla's add-on site. There's nothing you can do about this regardless of the gestures add-on you use - life is worse due to security concerns, this is why we can't have nice things, etc. And 2nd on Linux (maybe Mac too) Foxy Gestures did not work at all by default since the right-click menu triggers on mouse down, not mouse up. That stopped the gesture in their tracks. The FoxyGestures developer mitigated this problem by making right-menu take 2 clicks to trigger as an option enabled by default on Linux, but that can be annoying as now the regular right-click menu doesn't appear when you expect. Fortunately a patch is in Firefox for a future version that adds the option "ui.context_menus.after_mouseup", which makes the right-click menu work like on Windows. Also, a bonus, on Arch Linux the packager backported that preference to Firefox 57, so nice of them, which made everything work almost as well as in the pre-57 days.
- userbinator 9y agoIndeed, with all the CPU sidechannel attacks that just came out, allowing any untrusted code to run on your machine, even sandboxed in a browser, seems like a horrible idea.
- ChrisSD 9y agoI usually prefer to whitelist domains rather than individual scripts. Either I trust a domain enough to serve scripts or I don't, there's rarely a middle ground.
- fpoling 9y agoWell, typically a page does not run heavy calculations for minutes without any input/output. The ad blocker can use that.
- kodablah 9y agoI won't run a closed source ad blocker. Whatever my hypothetical nefarious self sees is the limit which triggers heavy-calc check, I'll just split my insns across requestAnimationFrame/setTimeout just beneath it. The cat-and-mouse game of ad blockers really should be no problem for the adversary (the ad companies) if they just put some thought and engineering into it.