SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
SoylentNews
posted by
cmn32480
on Sunday September 11 2016, @05:48PM
from the there's-gotta-be-a-downside-to-this dept.
from the there's-gotta-be-a-downside-to-this dept.
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.
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
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
QOTD:
"My life is a soap opera, but who gets the movie rights?"
(Score: 2) by NotSanguine on Monday September 12 2016, @03:04PM
Everybody ignores the importance of that one. Caching is good, https breaks it unless your ISP breaks https to fix it and that breaks security for those times you need it.
Caching is good only if bandwidth is a limited resource. Which it doesn't have to be.
What's more, I'd be happy with pages load ing a little slower (i.e., no caching) if it means my traffic can be encrypted.
I suppose that's just my personal preference, but it is my preference.
No, no, you're not thinking; you're just being logical. --Niels Bohr