8 ms·
I wonder how many site owners just disable https now.
by tomjen3 12y ago
I wonder how many site owners just disable https now.
- jfoster 12y agoGood point. There is potential for this to do more harm than good. The handling of insecure sites is very plain and non-alarming. The handling of https sites using SHA-1 is red & scary-looking. If the Chrome warning were clearer on what is wrong and what should be done to remedy it, there would be less risk of that happening.
- josteink 12y ago> If the Chrome warning were clearer on what is wrong and what should be done to remedy it, You mean if Chrome, like MSIE in the old days, had huge dialog windows with lots of text, which users learned to instinctively ignore and click away... This would somehow play out differently now than it did back then. It wont. I'm guessing lots of "lazy"/over-burdoned sysadmins will just disable HTTPS to make the Chrome-users shut up, and then he will forget about it, leaving the site HTTP-only.
- jasonmp85 12y agoAnd when Google starts penalizing their page in rankings because it's plaintext only? The sysadmins will hear about that from their bosses when visits drop.
- Someone1234 12y agoI actually agree. They should just yellow bar all the SHA-1 stuff. But will such a subtle approach force CAs to do the right thing? Unfortunately people have been bugging them for a long time, and it seems only a metaphorical gun to their heads has had any effect. I agree that HTTP being white and "happy" and SHA-1 giving the "DANGER WILL ROBINSON" scare alert, is inconsistent/wrong. That's more a HTTP issue however rather than a SHA-1 one (i.e. HTTP needs to be marked insecure).
- gsnedders 12y agoGoogle have done a lot of studies to try and reduce the number of click-throughs of TLS warnings, especially when it comes down to the wording of the message.
- jfoster 12y agoI don't mean they should present the message to all users. Currently, even if you go into the certificate details without being prompted, there is nothing there saying anything to the effect of "SHA-1 is insecure; if you are the webmaster, get this certificate issued with SHA-2"
- Someone1234 12y agoNone, I'd expect. This whole thing actually should never impact website admins. It is aimed to "encourage" CAs to do the right thing and stop publishing any NEW certificates with SHA-1. That's why they set the deadline for SHA-1 so far into the future, so that even if a certificate was created six months ago, it shouldn't have been impacted (when they first announced this). So if you just leave any SHA-1 certificates in place, and then when they naturally expire you get the replacement from your CA, that replacement should be SHA-256. You may not even notice. The only sites that MIGHT be impacted are sites who have CAs who are frankly asleep at the wheel. If your CA continued to issue 3 year certificates this year, you might be impacted, but I'd suggest you take that up with them and request they re-issue for free as SHA-256 (which they damn well better). A lot of people think half the internet will break, I disagree. If you look at the actual requirements (expiration date + SHA-1), very few sites right now fall afoul of that.
- toast0 12y ago> This whole thing actually should never impact website admins. I had to do a lot of work for this, because I need to support clients that can't accept a SHA-2 cert, as well as Chrome which won't accept my SHA-1 cert because it expires in 2016. The SSL termination I use didn't know how to do that, so I had to write a patch. Thanks a lot Chrome.
- deleted 12y ago[deleted]