Friday, May 18, 2018

Google Chrome is killing the URL security tag that highlights secure sites

Google Chrome green security tag

Google Chrome is going to remove the security indicator that highlights websites that are secure.

This is part of Chrome’s move towards a more secure web by making the Hyper Text Transfer Protocol Secure (HTTPS) — a secure protocol that encrypts communication — the default over Hyper Text Transfer Protocol (HTTP), which doesn’t encrypt data.

Since HTTPS sites will be the default in the future, Chrome reasons that it won’t need to reassure users about those sites. Come September with Chrome 69, HTTPS pages will no longer show the green secure tag. Instead users will get a small grey lock icon. Eventually, that grey icon will disappear as well.

Additionally, as of July’s Chrome 68 update, all HTTP pages will be marked with “Not Secure.”

Security Tags in Chrome

When Chrome 70 arrives in October, the team will implement the final stage of their master plan. All HTTP sites will be marked with a red “Not Secure” tag.

Why is this happening?

According to a blog post from Emily Schechter, the product manager of Chrome Security, too many sites still used HTTP to implement the change until now. But with over half the web using a secure connection now, it’s time to implement the change.

The goal for the Chrome team is a web that’s safe by default. That’s part of the reason the team is removing the green secure tag. Users shouldn’t need to be informed that a site is secure — it just should be. The other part is a hope that highlighting unsecured sites will make users pay more attention to their browsing.

Highlighted Not Secure tag

It remains to be seen how much this change will affect users. However, Chrome’s changes have definitely influenced websites.

We have a more secure web now. HTTPS isn’t perfect, but it’s better than nothing.

Source: Chromium Blog Via: Engadget

The post Google Chrome is killing the URL security tag that highlights secure sites appeared first on MobileSyrup.



from MobileSyrup https://ift.tt/2wTqrB3

Labels:

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home