Stories
Slash Boxes
Comments

SoylentNews is people

Google to Start Punishing HTTP-Only Sites

posted by cmn32480 on Sunday September 11 2016, @05:48PM   Printer-friendly
from the there's-gotta-be-a-downside-to-this dept.

SomeGuy writes:

According to a post on the Google Online Security Blog, beginning in January 2017 Google Chrome will begin flagging all sites that use traditional HTTP rather than HTTPS for passwords or other sensitive information as "insecure". It also indicates that Google plans to eventually start flagging ALL traditional HTTP-only sites as "insecure". While HTTPS has always made sense for truly sensitive information, a pure HTTPS web does have implications for legacy tools - essentially if anyone is not using the absolute latest of one of the "big three" web browsers, they will always potentially be just one security update away from being locked out of the web.

Original Submission

 
This discussion has been archived. No new comments can be posted.
Google to Start Punishing HTTP-Only Sites | Log In/Create an Account | Top | 63 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 0) by Anonymous Coward on Monday September 12 2016, @04:45PM

    by Anonymous Coward on Monday September 12 2016, @04:45PM (#400800)

    Yes, my sites are insecure. Intentionally so. I have nothing that requires encryption on either end.

    What was the problem with that again, Chrome? Anything worth reading needs to be secure? Oh.

    I guess you'll just have to deny everyone using your product from my website, then. Sorry, public! Not my fault that Google wants to force the Internet to be something it is not.