O Google yesterday announced another step towards the long road it takes in search of a fully encrypted internet based on secure connections. The Mountain View giant revealed that from the Chrome version 62, the browser will adopt a new behavior in the display of the warning "Not secure" for sites that do not present the HTTPS protocol.
Nowadays, the warning ?Not secure?, which appears next to the URL of a website without the HTTPS protocol, is displayed only when the user is typing in a sensitive information field such as a password or a credit card number. At all other times, the only warning that the site may have its security compromised is a small and not very flashy "i" circumscribed.
With Chrome 62, scheduled to reach the general public in October of this year, the behavior changes: on the pages in "common" tabs, the warning "Not safe" appears when the user is typing anything in any information field This is because Google believes that passwords and credit card numbers "are not the only information that should remain private", as stated in the official blog of the Chromium project.
For pages without HTTPS accessed through anonymous guides, the behavior will be even stricter: the warning ?No insurance? appears permanently, since the user who uses this type of guide is waiting from the start for a more advanced level of privacy and security although it is always good to remember that anonymous tabs are never a guarantee that your data will be totally preserved and out of sight whosesoever.
The idea of ??Google, of course, is to move towards behavior where all unsafe pages are identified as such permanently so that, over time, this will encourage developers and webmasters implementing the HTTPS protocol on its websites as a standard for the company itself, already highlights in its text that this process is increasingly easy and, in many cases, totally free. Really, there is no more excuse, is there?