Google has taken a slow approach to this change, as there are a number of popular plugins that rely on it, most notably Java and Silverlight, which are used in various ways across the Web. Because of this, Chrome will be phasing out NPAPI support over the coming year,” Justin Schuh of Google wrote in September 2013. Meanwhile, NPAPI’s 90s-era architecture has become a leading cause of hangs, crashes, security incidents, and code complexity. “Today’s browsers are speedier, safer, and more capable than their ancestors. But the NPAPI isn’t necessary in today’s world and causes more problems than it solves. It was the first real way for developers to add functionality to browsers, which were still emerging at the time. The company began requiring users to click to run plugins that rely on the NPAPI, an ancient API that was designed to help extend the functionality of browsers. Google warned developers and users about it more than a year ago and gradually had changed the way Chrome handles some plugins. But the most significant security change in the new browser is Google’s decision to disable the NPAPI, essentially turning off plugins such as Java and Silverlight by default. With the release of Chrome 42 this week, Google fixed more than 40 vulnerabilities.
0 kommentar(er)
