The new version brings two small news along with 37 fixes security, but do not expect a revolution.
Google has recently launched Chrome 48 on Windows, Linux and Mac, the latest release of the company’s own browser. This mainly introduces the custom keys for notifications and removes the RC4 encryption, but there will be no tangible innovations, specifically for the end user. Instead, it improves safety thanks to 37 fixes security made thanks to the contribution of internal and external teams who relies now.
More than just a browser, we may consider Chrome as a complete platform. It has over 1 billion users and is an ecosystem that many developers are forced to consider, together with its rhythmic changes over time. One of the news is on the push notification system, a feature that integrates Chrome apps and extensions from May of 2010 (on Chrome 5 for the first time), and the Web sites from release 42.
Google recently removed the notification center on the platform. However, Chrome continues to deliver more than 350 million push notifications each day and it is clear that the company wants to focus on the feature. From Chrome 48, sites can add custom buttons to the notifications, even on the mobile, in order to facilitate the users to complete the desired action directly from the same notification.
The other important change in Chrome 48 is the elimination of the support RC4 encryption over HTTPS connections. Designed in 1987 RC4 it has been widely used by various browsers and online services for the protection of data via encryption. Over the years, he proved not to be the most reliable solution in terms of safety because of several vulnerabilities that allowed any cracker around it in a few days, sometimes in a matter of hours.
Last February, a series of new attacks has prompted the IETF to prohibit the use of RC4 with TLS, with all the major names in the field of web browsing that have promised to drop support of security on their respective web browser technology. The first to do so would seem right with the new Google Chrome 48. If you attempt to launch a web page protected by RC4 with the new release everything that you get is an error page.
The Chrome 48.0.2564.82 m installation (the latest at the time of this writing) automatically if you have the appropriate settings enabled. Otherwise, the user can choose to force the update from the application’s settings.