SoylentNews is people
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.
Besides, REAL computers have a rename() system call. :-)
-- Larry Wall in <7937@jpl-devvax.JPL.NASA.GOV>
(Score: 2) by NotSanguine on Monday September 12 2016, @02:58PM
How exactly does verifying a cert protect anyone?
Not very much. However, encrypted communications across the internet keeps prying eyes that don't control the endpoints from viewing your traffic.
HTTPS is as much (or more) about encryption as it is about identity.
No, no, you're not thinking; you're just being logical. --Niels Bohr