News for hackers. Stuff that matters.
Re:Inside Firefox’s DNS-over-HTTPS engine by watermelon0 on Monday June 04, 2018 @04:06AM (#17225546)
If malware can modify /etc/hosts, then it shouldn't have any problems modifying Firefox executable or, even easier, it's configuration.
Re:Inside Firefox’s DNS-over-HTTPS engine by geofft on Monday June 04, 2018 @11:05AM (#17228415)
This is true, but most malware is neither high-effort nor high-quality. It's very easy to edit /etc/hosts. It's a lot harder to inject yourself into the binary in a way that works. It's harder still to inject yourself into the binary in a way that works if the binary is actively trying to not be injected into, or using some security-by-obscurity scheme for signing the config, or whatever. Yes, it's all running at the same privilege level (or lower) and the malware technically has the access, but it's not cost-effective to have battle-hardened automatic reverse-engineering tech built into your malware.

Chrome in particular has a DLL blacklist that seems to work very well in practice: in theory, a DLL blacklist can't possibly work, but in practice, DLLs don't try hard enough to hide their existence from the blacklisting code. https://www.chromium.org/Home/third-party-developers#TOC-Goo...

Re:Inside Firefox’s DNS-over-HTTPS engine by crtasm on Tuesday June 05, 2018 @06:24AM (#17236357)
Yes but you don't need any of that in this case, Firefox's config files are easily editable to toggle am option like using DoH.