Chrome: even HTTPS can be insecure

Chrome: even HTTPS can be insecure

After having personally contributed to promoting the dissemination of websites under protocol HTTPS (HyperText Transfer Protocol over Secure Socket Layer), choice then followed by all the most important competing Web browsers, Chrome is preparing to make even more stringent the criteria that define safe or insecure user navigation.

In contrast, starting from 2020 the application should start to block all the contents considered risky even if present in an Internet site loaded under HTTPS. Among the elements involved in the block there should be scripts, videos, iframes and all the other page components that could give rise to malicious activity.

If everything goes as planned, the first browser release of Google 79 features for December 2019 are expected to present this partially enabled feature. Clearly there will be options specifically dedicated to customization, thanks to which users can decide to unblock the contents of Internet sites they consider harmless.

To do this, simply click on the "padlock" displayed in the URL bar and scroll the menu so open to the item Site settings ("Site settings" in Italian localization). This will make one available whitelist in which to add and list all the web pages that should not be blocked.

The definitive consolidation of the new functionality should take place with the release of the 80 versions, which will indicate by default as "unsafe" the contents considered dangerous, and 81, which will proceed by default to load the components over HTTP (ie unencrypted) via HTTPS and to block them if this procedure is not possible.

You May Also Like

Leave a Reply

Your email address will not be published. Required fields are marked *