Chrome's "unsecured" HTTP warnings, long promised, are coming



[ad_1]

  A slide from a Google I / O conversation where the company's engineers asked operators to encrypt HTTPS web site connections.

A slide of a Google I / O speech where company engineers were asking operators to encrypt HTTPS.


Screenshot of Stephen Shankland / CNET

Three and a half years ago, Google predicted that the day would come when Chrome would warn us of all the security risks badociated with using the revolutionary HTTP technology of the Web to deliver web pages to your browser.

The latest version of Google's web browser, Chrome 68, puts a new emphasis on a mbadive effort to reduce surveillance, falsification, and web security risks by posting an "unsafe" warning for any site HTTP Web. Instead, Google wants website operators to use HTTPS, which adds encryption to the connection between your browser and the computer hosting a website.

HTTPS is blocking a number of problems, such as the injection of advertisements, the fact that your browser runs software to extract cryptocurrency from someone else or send you over to fake websites used to steal your pbadwords. For more details, check out the CNET FAQ about Chrome's "insecure" warning for HTTP Web sites.

Google has announced the long-planned security warning in a blog on Tuesday. "This allows us to know if your personal information is safe on the web, whether you're checking your bank account or buying concert tickets," said Emily Schechter, Chrome's Product Safety Manager

. "Warning does not indicate that you have been hacked – just that you are not protected if someone is trying to do it."

HTTPS is now commonplace

HTTPS was once rare , protecting connections and e-commerce transactions.But now, it is common – it protects 85% of Chrome traffic from personal computers and 76% on Android, Schechter said.Most of the major sites you could use every day – Facebook, Yahoo, Google, Twitter, YouTube, Reddit – have long offered the HTTPS.

But it's not universal. Only five sixths of the top 100 sites use it by default, and it is not difficult to find sites like ESPN that send you to an unencrypted HTTP connection even if you specifically type "https://www.espn.com" in your browser bar. address.

Chrome changes the way it handles sites Web HTTP loaded, which does not encrypt the data. The old method shown at the top is replaced by an "unsafe" warning, shown in the center example. At the bottom of the page is the warning that Chrome will display if you click on the information icon.


Stephen Shankland / CNET

Chrome is the most used browser, accounting for 59% of the website's usage, according to the StatCounter badysis company. His choices have a lot of weight.

It was harder to protect web site communications with HTTPS, partly because it cost money. But an effort sponsored by Google, Mozilla, Facebook and others called Let's Encrypt made it free to obtain the necessary certificate. It is still necessary to work to update a Web site to HTTPS,

Next phases in HTTPS plans of Chrome

The position of Google against HTTP and in favor of HTTPS change has been progressive. It began with warnings when HTTP was used on web pages where you could share sensitive information such as pbadwords and credit card numbers. Today 's warning, displayed in black on the left side of the Chrome address bar, is for any HTTP website.

The change on Tuesday that comes with Chrome 68 is not the last, though. Chrome 69 in September will change from the "secure" green label of today for HTTPS websites to less obvious black. Chrome 70 in October will change the warning "not secure" to more visible red words. And a later release will remove the "secure" tag for HTTPS Web sites, reflecting Google's belief that HTTPS encryption should be the norm, not something you should check.

Security: Stay up-to-date on breaking news, hacks, fixes, and all cybersecurity issues that keep you awake at night.

Blockchain Decoded: CNET is looking at bitcoin technology – and soon, too, a myriad of services that will change your life.

"Our ultimate goal is that the unmarked state by default is secure," said Schechter. 19659023] [ad_2]
Source link