News for hackers. Stuff that matters.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by no_protocol on Thursday December 08, 2016 @09:36PM (#13136254)
So if I just redirect all http requests to https, what unexpected consequences might I run into?

Not-for-profit hobby site/community with a couple hundred regular users. Have been running https with Let's Encrypt certs for a year but not advertising or defaulting to it. No legacy systems or other entanglements.

There is a forum that allows users to post inline images and media from other domains.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by hughes on Thursday December 08, 2016 @09:39PM (#13136273)
If you load any external scripts that are not secure, they might no longer work. Chrome blocks such scripts by default[1].

Depending on your server setup, if you run multiple web domains from the same server then web clients that do not support SNI may fail[2].

[1] https://support.google.com/chrome/answer/1342714

[2] http://stackoverflow.com/q/21956663/796554

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by regecks on Thursday December 08, 2016 @10:44PM (#13136504)
If you have absolute URLs (http://..../foo.jpg) saved in documents or a database or something like that, you would need to rewrite them to be protocol-relative or just https:// .
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by ReverseCold on Thursday December 08, 2016 @11:00PM (#13136560)
Hmm, but they said SSL is already enabled if you visit the site with https. Shouldn't redirecting http > https be completely risk free then or am I missing something?
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by chipperyman573 on Thursday December 08, 2016 @11:24PM (#13136666)
If you visit a secure site (https), embedding insecure items (http) will fail because they could do just as much damage as loading the entire page over http.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by Buge on Friday December 09, 2016 @01:53AM (#13137159)
It depends on what the insecure item is. If it's just an image, it won't fail, it will just grey out the https and not display a lock icon.

https://mixed.badssl.com/

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by nailer on Friday December 09, 2016 @07:11AM (#13138282)
That's current behavior, but I wouldn't guarantee it will remain that way, an http image compromises the integrity of the site: it could be manipulated to change the meaning. Imagine reading a news site using an unencrypted CDN and whoever runs the WiFi (or the country you're in) is replacing the images with similar yet different ones, giving a different impression that what the creator intended.

You could do this quite subtly as a way to influence people by making certain figures appear more sinister.

These warnings tend to get tougher over time, so what's grey now may be red next year.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by CharlesW on Thursday December 08, 2016 @11:18PM (#13136636)
I think the reply was suggesting that "not advertising or defaulting to [HTTPS]" implies that a quick check for absolute HTTP URLs would be Good Thing.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by colemickens on Friday December 09, 2016 @12:12AM (#13136817)
Basically every single reply to the GP is making the same point about http assets loaded from a page loaded over https...

Surely the GP wouldn't have asked the question they did if their https site was already broken...

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by rogerdpack on Friday December 09, 2016 @12:34AM (#13136889)
Appears it should be OK unless some inline embedded images are hard coded to "http://" in which case the browser will, I believe, refuse to even try and load them, so you may need to fix that. If they're all relative you're good to go :)
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by discreditable on Friday December 09, 2016 @10:41AM (#13139305)
In the future, the upgrade-insecure-requests CSP directive[1] might help with this problem. I'm not sure what browsers have implemented it yet though.

1. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Co...

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by davidgerard on Friday December 09, 2016 @04:16AM (#13137627)
IME, mixed-content warnings. Tracking down those can be a nuisance. If users can add inline images, you'll basically not be able to avoid these.

Let's Encrypt certs work on pretty much every device. (Some Comodo certs don't work on older Android, for instance - we hit this at work and switched those sites to Let's Encrypt, problem solved.)

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by byuu on Friday December 09, 2016 @09:26AM (#13138888)
You mentioned community. If you have a forum or message board where people can select their own avatars or post image links, then you'll enjoy the land of mixed content warnings.

Add the header "Content-Security-Policy: upgrade-insecure-requests" and the mixed content errors will go away, but you'll experience a new problem.

About 30% of images/avatars will break, and of those, roughly 10% of them will cause the page loading animation to keep going for 2-3 minutes before finally timing out. I presume this is due to some sort of server misconfiguration on their part, as most non-HTTPS sites fail fast.

Give it a few months and users will slowly update their avatars and stick to sources that support HTTPS (like imgur), but don't expect the problem to ever go away completely.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by londons_explore on Friday December 09, 2016 @09:57AM (#13139052)
Run a reverse proxy to host all the user content on your own domain under https instead.

Eg. https://yourdomain.com/usercontent/worldofcats.com/foobar.jp...

There exist simple php scripts which can do that for you. Beware to sanitize the URL very well, and probably enforce file size rules.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by robryk on Friday December 09, 2016 @11:52AM (#13139855)
Don't do this on your domain. Have a separate domain for user content (and, if the content isn't public, better have many separate domains and distribute the content between them; maybe even have a per-user domain). Browsers can be convinced that a particular resource is an html page even if the content-type is wrong.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by mpclark on Friday December 09, 2016 @05:49AM (#13137968)
Just did this this week. The only unexpected effect I found was that all our Facebook likes were reset to zero. FB must consider the two versions of each page as being separate and different.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by askvictor on Friday December 09, 2016 @06:28AM (#13138116)
What type of redirect did you implement? Just curious; this sounds somewhat like the cname vs redirect argument for www. to bare domain name.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by mpclark on Friday December 09, 2016 @07:15AM (#13138291)
It's a Nginx directive that rewrites requests from http to https with a 301
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by nkozyra on Thursday December 08, 2016 @11:52PM (#13136757)
Well, there is still overhead for using HTTPS, particularly for the handshake. This is unlikely to be palpable at your size, though.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by Klathmon on Friday December 09, 2016 @06:40AM (#13138165)
The overhead is negligible with the prefetching browsers do, and even that is closing fast with things like TCP fast-open.

Plus TLS false start and TLS resumption are already here and work great for repeat visits to remove that extra overhead.

Performance isn't an excuse for not using TLS anymore.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by nkozyra on Friday December 09, 2016 @09:47AM (#13139008)
Oh I agree it's no excuse, OP just asked what the tradeoff/cost was. There is still some but as you say it's negligible and especially so for a very small site like that.