Mozilla Firefox will quickly block the injection of DLLs by antivirus functions and different third-party applications in an effort to enhance stability, safety, and privateness.
Antivirus functions on Windows and different third-party functions, e.g. different safety software program or PDF instruments, might inject DLLs within the browser. These injections are recognized to trigger stability points for customers.
Mozilla follows Google which began to block third-party code injections in Google Chrome in 2018. Google found that Chrome installations with third-party DLL injection crashed 15% greater than Chrome installations with out.
Mozilla started to analyze choices to disable DLL injections in Firefox within the fourth quarter of 2016 however issues picked up velocity solely not too long ago.
Firefox Nightly, the leading edge model of the Firefox browser, blocks DLL injections already. The function will be built-in in Beta and Release variations of the Firefox browser after they hit model 66.
Firefox Beta will hit model 66 on January 29, 2019, and Firefox Stable model 66 on March 19, 2019 according to the release schedule.
How are you aware whether or not the protecting function is enabled already? That’s straightforward. Just open about:assist within the browser’s handle bar and verify the Launcher Process itemizing close to the highest.
If it states enabled it’s energetic; if it states disabled or will not be current, it’s inactive.
Firefox customers can disable the function at present and it’s doubtless that the turn-off possibility stays a function in Beta and Stable as nicely.
Go to about:config?filter=browser.launcherProcess.enabled to show the choice in Firefox. Note that the hyperlink returns the choice provided that it exists.
Double-click on it to set it to True or False. True signifies that the launcher course of is enabled, False that it’s disabled. Firefox blocks DLL Injections by third-party functions if the choice is ready to true.
Firefox customers (and Chrome customers) might expertise points with their browsers or functions that try to inject DLLs into the browsers. Third-party builders might must replace their functions to take away the DLL injecting parts from the functions or exclude browsers that block these try anyway.
DLL injections have all the time brought about stability points on Windows; Google found a 15% extra crashes in Chrome browsers with DLL injections than with out. Mozilla didn’t reveal any statistics however it’s doubtless that the determine is in the identical area. (by way of Techdows)