SoylentNews is people
SoylentNews
from the wasn't-worth-the-work...-until-now? dept.
Submitted via IRC for AndyTheAbsurd
As of today, Google begins shipping Chrome 68 which flags all sites served over the HTTP scheme as being "not secure". This is because the connection is, well, not secure so it seems like a fairly reasonable thing to say! We've known this has been coming for a long time now both through observing the changes in the industry and Google specifically saying "this is coming". Yet somehow, we've arrived at today with a sizable chunk of the web still serving traffic insecurely:
The majority of the Internet’s top 1M most popular sites will show up as “Not Secure” in @GoogleChrome starting July 24th. Make sure your site redirects to #HTTPS, so you don’t have the same problem. @Cloudflare makes it easy! #SecureOnChrome https://t.co/G2a0gi2aM8 pic.twitter.com/r2HWkfRofW
— Cloudflare (@Cloudflare) July 23, 2018
Who are these people?! After all the advanced warnings combined with all we know to be bad about serving even static sites over HTTP, what sort of sites are left that are neglecting such a fundamental security and privacy basic? I wanted to find out which is why today, in conjunction with Scott Helme, we're launching Why No HTTPS? You can find it over at WhyNoHTTPS.com (served over HTTPS, of course), and it's a who's who of the world's biggest websites not redirecting insecure traffic to the secure scheme:
The article continues with a list of "The World's Most Popular Websites Loaded Insecurely", tools and techniques used to gather the data, different responses based on the version of curl, differences accessing the bare domain name versus with the "www." prefix, and asks for any corrections. One can also access the aforementioned website set up specifically for tracking these results: https://whynohttps.com/.
(Score: 2) by c0lo on Wednesday July 25 2018, @12:58PM (3 children)
Unless the hosting entity does not share the private key with the feds, this cannot happen - correctly done, the private key should never leave the server.
The private/public key pair is generated on the server, then the public key goes with the Certificate Signing Request to the CA but the private key should (ideally) never leave the server that would host the Web Server.
https://www.youtube.com/watch?v=aoFiw2jMy-0
(Score: 0) by Anonymous Coward on Wednesday July 25 2018, @02:16PM (1 child)
i thought this was all about google maintaining better control of data via the fact it doesnt matter if its encrypted if they host it, and second, its good pr to pretend they care.
people lost control a long time ago, so this at least is like a politician being 'tough on crime' by doing nothing much themselves aside from providing severe punishment that doesnt fit the crime.
(Score: 2) by c0lo on Wednesday July 25 2018, @02:35PM
Speaking of which... What exactly is the malfeasance Google is accused of if Chrome signals to the user a site using plain HTTP is insecure? It's not like they are lying, is it?
https://www.youtube.com/watch?v=aoFiw2jMy-0
(Score: 0) by Anonymous Coward on Wednesday July 25 2018, @08:40PM
The Feds can decrypt SSL traffic no problem. It would give them a slightly higher overhead but not crazy. The real safety comes from making it hard for non-gov criminals to find the desired traffic. The problem you are having is assuming the crypto and the hardware it runs on doesn't have flaws. They don't even have to be full backdoors since some small flaw in the encryption routine can make it much simpler to crack the encryption if you know what pattern to look for.