The coronavirus has made many software development will stagnate or postpone until workers can return to their usual spots. It is the case of Google Chrome 82, that the company will jump to bring all of its features to Chrome 83 from the different channels.
However, Chrome 81 is already reaching millions of computersas Firefox 75 yesterday, and comes with some interesting features in terms of safety and functionality, especially for administrators, who will have to analyse if it does not impact your website. The mobile version of the browser come important new features such as improved support for augmented reality or NFC support for the web, but we will focus on the functions of desktop.
32 security patches as most relevant to the user
The new Google Chrome 81 comes with 32 security patches, in which Google has spent a total of 26,500 dollars as a reward to researchers external to the company. Three of them are with high severity, eight had medium severity, and twelve are low severity. In any case, it is always the first thing that we should take into account at the time of update.
As we can see in the image, the web applications progressive (PWA) can now use a badge notification in the Dock in macOS or in Windows 10 to show that there are new developmentsas a new mention on Twitter, a new e-mail, etc, This feature was already available in the channels beta, but now comes to the stable version.
In terms of other new features of Chrome 81, there is talk of TLS 1.0 and 1.1. The company wanted to eliminate such protocols in Chrome 81 in marchbut the launch was postponed and, in full pandemic, such action has been postponed to Chrome 84that , waiting to be released in July of this year.
The removal of the support of TLS old responded to their replacement by other, more modern and much more safe, but even so, there has been a change in this direction. TLS 1.0 and 1.1 are now considered obsolete, and on the websites that do not use TLS 1.2, the web browser will display a warning that the connection is not completely secure. Web administrators can disable these warnings until January of next year.
In addition, as we already have last week, Google Chrome 81 will now try to upload all the images HTTP addresses to the equivalent HTTPS, rewriting the calls in the HTML. If the browser does not find secure resources, Google Chrome 81 you can now block your load. In the Chrome 80 already been done with audio and video, and the idea is that the websites you go implementing these resources much more secure.
Via | Venturebeat
it was originally published in