Google Will Block Third-Party Software From Injecting Code Into Chrome (bleepingcomputer.com)

Catalin Cimpanu, writing for BleepingComputer: Google has laid out a plan for blocking third-party applications from injecting code into the Chrome browser. The most impacted by this change are antivirus and other security products that often inject code into the user's local browser process to intercept and scan for malware, phishing pages, and other threats. Google says these changes will take place in three main phases over the next 14 months. Phase 1: In April 2018, Chrome 66 will begin showing affected users a warning after a crash, alerting them that other software is injecting code into Chrome and guiding them to update or remove that software. Phase 2: In July 2018, Chrome 68 will begin blocking third-party software from injecting into Chrome processes. If this blocking prevents Chrome from starting, Chrome will restart and allow the injection, but also show a warning that guides the user to remove the software. Phase 3: In January 2019, Chrome 72 will remove this accommodation and always block code injection.

Comments

"Injecting" vs. "Plugging in"

[mi]

Google Will Block Third-Party Software From Injecting Code Into Chrome

What's the difference between "plugging in" and "injecting"? Spin!

Availability of plugins is good, threat of injections is terrifying. The technically-important differences? I don't see any...