3 ms·
Should Mozilla (or any other group) get to decide what I can or cannot do to a process running on my hardware, even if it originated from them? Things like this
by userbinator 3y ago
Should Mozilla (or any other group) get to decide what I can or cannot do to a process running on my hardware, even if it originated from them? Things like this make me feel uneasy because it seems to be sitting on the edge of a slippery slope.
Another example of these "silently user-hostile" applications is VirtualBox; it spawns multiple processes in a similar way, and even resists attempts to debug it if it's already running. I remember being incensed enough by it complaining about my --- patched to make the OS work for me and no others --- system DLLs not matching its internal whitelist and not starting, but not after I exercised the same skills to patch out those checks in it.
- rzzzt 3y agoIt looks like you get to decide which DLL can stay and which one will be blocked from loading. When do you expect the shiny ball of control to be taken away from users?
- CJefferson 3y agoI don't understand how you can be so negative. The title literally says it is giving users that power. This is empowering you, by giving you the ability to see which DLLs are being injected into Firefox. They do block some by default, certainly, but only ones which in practice just crash Firefox (often because they are old).
- userbinator 3y agoTo need to be "giving" something that should be, for lack of better phrasing, a given, is not a good sign. They do block some by default, certainly, but only ones which in practice just crash Firefox (often because they are old). Is there a way to unblock them as easily as blocking them?
- drdaeman 3y agoI can't test this, but I suppose it should be as easy as going to about:third-party and clicking a button next to a blocked entry. Probably preemptively learning about how to reset this if Firefox won't start anymore. As long as it's all end user-controlled, I suppose the only issue is awareness that this feature exists and how it's controlled (this is the first time I've read about it). Also, it feels somewhat weird to have this function in an application rather than at the OS level (or as a independent process firewall application) - but I suppose this is fine.
- Dylan16807 3y agoYeah it should be a given that you have control over this. Blame your OS for the fact that you don't have it by default. It doesn't make any sense to get mad at firefox for implementing this. They're not interfering with your control. If they did nothing, you would have no control.
- AstralStorm 3y agoInterestingly enough, Windows has this feature since Windows 10, but the PE flag disabling injection has to be set or an exception in security settings added to engage it. The latter is how Microsoft secures Protected Container in Edge. It's not particularly easy to set up and is just a complete block. The options are called Arbitrary Code Guard, Code Integrity Guard and (for old versions) Disable extension points. https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/customize-exploit-protection?view=o365-worldwide https://learn.microsoft.com/en-us/microsoft-365/security/def...
- nubinetwork 3y agoThat would imply I had the choice to begin with. On my work PC, they inject various plugins to enforce security policy. I imagine if I tried to circumvent that, the security software would just terminate the browser entirely. Not going to try, it's not worth it for me.
- nitwit005 3y agoIt's open source software. Comment out the whole feature if you want.
- userbinator 3y agoPatching the binary is easier than trying to rebuild Firefox (especially if you don't want anything else to potentially change.)
- TheBrokenRail 3y agoThis is really minor compared to other parts of Firefox. Notably, Firefox requires all extensions to be signed by Mozilla. And the only way to turn that restriction off, is to either use Firefox Nightly or Firefox Developer Edition (which is a beta). If you want to use stable Firefox, because you like having a stable web browser, you just can't turn the restriction off. Period. The closest thing you can do is installing it as a "temporary extension" which uninstalls itself when the browser restarts. It's kind of ridiculous that the default browser of most Linux distros has a Apple-esque mentality of "we get to tell you what you're allowed to install."
- emn13 3y agoI think it's unreasonable to assume the vast, vast majority of users, including technically literate ones, are likely to have an in detail understanding of any specific software's installation. Requiring a few hoops - and it sounds like e.g. requiring a developer edition sounds like such a hoop - to ensure a likely misconfiguration was actually intentional and the user is capable of dealing with the consequences is not a bad idea. In particular, debugging when things go wrong can be an insurmountable task. Better isolation of software components has been a trend for decades; to the point where I think we can safely say that the old unix and windows model of permissions was a fundamentally insufficient idea. Devs flock to using VMs and containers precisely because uncontrolled interaction between stuff even controlled by the same nominal "user" is a huge pain - and that's before malware and privacy concerns come in. Were software more isolated by default, and interaction more controlled and/or explicit, then indeed I think the argument against this kind of controlling-the-"user" features would be stronger. But as is? The alternative is clearly much, much worse. After all, certainly here and often in other cases too - it's not like it's actually impossible to circumvent these restrictions. It's simply technically inconvenient in a way that happens to also prevent many unintentional bugs and some malware vectors. In an ideal world, a devs for a piece of software would be hard-pressed to even do this, let alone feel the need to do it. But that's just not the world we live in; we're not even really close yet - except on really locked down platforms that go much further than needed to prevent the risks, and into the territory of quite openly restricting the user, not the software.
- ComodoHacker 3y agoHave you ever maintained a product popular enough that lots of people try to hack into and abuse? If yes, you should understand the reasons for protective measures like this.
- deelly 3y agoLike Chrome, Windows, Android, iOs etc? We all understand that companies wants to protect us from "evildoers". But its a similar situation as with any censorship. Why not allow users to decide themselves?
- theamk 3y agothat's exactly what they did. Have you read the article?
- deelly 3y agoDid we read different articles? This functionality is enabled by default. That`s why I`m asking - why don't ask the user first? Upd: please be civil, this is a discussion and not a competition.
- theamk 3y agoWell, as the article said, there is an user-selectable option, so the answer to "Why not allow users to decide themselves?" is "they did" As for default, that's a different question unrelated to user freedom. Unfortunately in Windows, DLL injection is very often abused for no good reason. Imagine a simple, non-technical user getting asked about permitting mouse driver DLL.. what would user think? With only information being DLL name/description, they might think that mouse will not work without it and permit it (see https://news.ycombinator.com/item?id=36681873 https://news.ycombinator.com/item?id=36681873 for real reason). And once firefox starts crashing, will they know how to disable it? No, it is much safer to disable it all by default. And if a powrer user needs a specific DLL, they can enable it. As a bonus, they will learn where the dialog is, so they can disable it back once the crashes start.