Google Chrome for Windows will block injections of third-party code to reduce crashes – tech2.org

Google Chrome for Windows will block injections of third-party code to reduce crashes



[ad_1]

  Chrome icons

When Google announced Chrome almost a decade ago, one of its promises was to offer a more stable browser. The company used sandbox techniques to make sure that if a process on one tab fails, it will not tear down the rest of the browser with it. At first, it almost seemed that the browser could not be blocked, but the reality is that nothing is impossible to erase.

Eventually, once user applications started linking to Chrome, the browser became immediately more vulnerable to failure. It is not difficult to understand why: if you inject code into a running application, there is no reason to expect it to handle it correctly. Google says that people running apps that inject code into Chrome are 15% more likely to experience crashes.

  HotHardware Chrome

We came to a time when the Internet is used for more than killing time. We trust him, so Google wants to make sure there are no locks that prevent our navigation. This coming April, with Chrome 66, the company will begin to get people out of solutions that require code injection.

With Chrome 66, users will receive a message after an accident that will explain what happened, and then suggest that they remove or update the software. In the case where an update is all that is needed, it is likely because the software provider switched to other techniques, such as relying on extensions instead of direct injection.

  Chrome Anti-Injection Warning
Affected users will begin to see messages like these in the near future

A couple of months later, in July, Chrome 68 will decline and start rejecting code injections, but there is a warning. If in some way the injection of code is required for the browser to work, after its initial block, it will restart and then allow the injection to be made. Again, the messages will alert the user to what the problem is, how to fix it and why it will be an even bigger problem in the future, once Chrome 72 starts.

We are really looking to the future now. In January 2019, Chrome 72 will block the code injection 100% of the time. That gives software providers, such as those who produce antivirus products, a lot of time to work on alternative solutions, such as using a browser extension. Google notes that the code signed by Microsoft, the accessibility software and the IME software will not be affected by these changes. The company also suggests that developers choose to use the beta version of Chrome, to perform more efficient and effective tests. It is not a bad idea, because if your software solution is responsible for blocking someone's browser, that client will inevitably look for alternatives.

[ad_2]
Source link

Leave a Reply

Your email address will not be published.