Chrome 95 arrives with a new sidebar, says goodbye to FTP and also prepares to fire User-Agent

Google Chrome

Few days ago Google announced the launch of the new version of the Chrome 95 web browser in which other innovations and bug fixes, the new version removes 19 vulnerabilities, many of which were identified as a result of automated testing with AddressSanitizer, MemorySanitizer, LibFuzzer, and AFL

No critical issues have been identified that would allow bypassing all levels of browser protection and running code on the system outside of the sandbox environment. As part of the Vulnerability Cash Bounty program for the current version, Google has paid 16 bonuses worth $ 74,000.

Chrome 95 main news

In this new version for Linux, Windows, macOS and ChromeOS users, a new sidebar is offered, displayed to the right of the content and is activated by clicking a special icon in the address bar. The dashboard displays a summary with bookmarks and a reading list. This change is not enabled for all users and to activate it is done from “chrome: // flags / # side-panel”.

Another of the changes that stands out is that the output of an explicit request for permission to save addresses entered in web forms was implemented for later use in the form autocomplete system.

We can also find that in this version the code was removed for compatibility with the FTP protocol, Since Chrome 88, FTP support was disabled by default, but the mark was left to revert it. Additionally sand removed URL support for numeric hostnames terminated on the host that do not match the IPv4 addresses.

For WebAssembly, the ability to create exception handlers is implemented which can trap execution if an exception occurs while certain code is running. Supports both known exception trapping by the WebAssembly module as exceptions during the call of imported functions. To catch exceptions, the WebAssembly module must be built with an exception capable compiler such as Emscripten.

In addition, the truncation of the information in the HTTP header of the User-Agent and the JavaScript parameters navigator.userAgent, navigator.appVersion and navigator.platform was enabled. The title contains only information about the name of the browser, the significant version of the browser, the platform and the type of device (mobile phone, PC, tablet). To get additional data, such as the exact version and extended platform data, you must use the User Agent Client Suggestion API. The start of the User-Agent cutback on normal user systems is scheduled for the release of Chrome 102, which will be released in half a year.

The secure payment confirmation API has been stabilized and is offered by default with the implementation of the new ‘payment’ extension, which provides additional confirmation of the payment transaction in progress. The verifying party, for example a bank, has the ability to generate a PublicKeyCredential public key, which the merchant can request for additional secure payment confirmation via the payment request API using the payment method ‘payment confirmation safe’.

On the other hand the U2F API (Cryptotoken) it is deprecated and should use the web authentication api instead. The U2F API will be disabled by default on Chrome 98 release and will be completely removed in Chrome 104.

Of the other changes:

  • Improvements have been made to the web developer tools.
  • The styles panel makes it easy to adjust size-related CSS properties (height, padding, etc.).
  • The Issues tab offers the ability to hide individual issues.
  • Improved display of properties in the web console and in the Fonts and Properties panels (custom properties are now bold and displayed at the top of the list).

How to update or install Google Chrome in Ubuntu and derivatives?

For those who are interested in being able to update to the new version of the browser on their systems, they can do so by following the instructions that we share below.

The first thing you should do is check if the update is already availableTo do this you have to go to chrome: // settings / help and the notification that there is an update will appear.

In case it is not so you must close your browser and open a terminal and type:

sudo apt update

sudo apt upgrade 

You open your browser again and it must have already been updated or the update notification will appear.

In case you want to install the browser or choose to download the deb package to update, we must go to the web page of the browser to obtain the deb package and to be able to install it in our system with the help of the package manager or from the terminal. The link is this.

Once the package is obtained, we only have to install with the following command:

sudo dpkg -i google-chrome-stable_current_amd64.deb

Finally, it is also worth mentioning that Based on the new 4 week development cycle, the next version of Chrome 96 is scheduled for November 16. For those who need more time to update, the Extended Stable branch is supported separately, followed by 8 weeks, in which an update has been generated for the previous version of Chrome 94.

Add Comment