News for hackers. Stuff that matters.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by kuschku on Thursday December 08, 2016 @10:03PM (#13136348)
So, how do I manage a website where I allow users to embed arbitrary URLs as image, so I don’t even know which protocol they’ll use, but where I want HTTPS for the page itself?

Will I just have to deal with the yellow "mixed content! insecure!" warning? Will I have to proxy requests?

There’s many forums like that in the web.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by TheCoreh on Thursday December 08, 2016 @10:18PM (#13136416)
You could (and in fact probably should) do what GitHub does. Fetch the images, store a copy and serve them yourself. That way even if the external URLs stop working, the images on your forum/site will remain functional.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by no_protocol on Thursday December 08, 2016 @10:21PM (#13136427)
This is scary to me so I haven't tried it yet. If I'm allowing users to upload arbitrary files, I might have to deal with things like copyright laws. It doesn't sound fun. Does anyone have relevant information for such a site in the United States?
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by ldjb on Thursday December 08, 2016 @10:36PM (#13136473)
I'm not a lawyer (nor even American) but I believe the most relevant legislation would be the Digital Millennium Copyright Act. In which case, it might be a good idea to formulate a policy similar to the one linked to in the footer of this very website.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by catmanjan on Friday December 09, 2016 @12:25AM (#13136859)
It's not a trivial problem, I'd be more worried about users uploading illegal content maliciously. Would definitely require a moderation team depending on the site size...
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by vbezhenar on Friday December 09, 2016 @07:55AM (#13138462)
AFAIK hosting a link could be copyright violation too. All bittorrent sites host links, not real content, yet they are sued and closed.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by hughes on Thursday December 08, 2016 @10:08PM (#13136374)
You can try adding `upgrade-insecure-requests`[1] to your page

[1] https://developers.google.com/web/fundamentals/security/prev...

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by rogerdpack on Friday December 09, 2016 @12:36AM (#13136895)
In the short term, as long as you don't have any password/CC prompts, you can continue using HTTP.

In the long term you'd have to "hope" the whole web transitions to https and just rewrite the url's to https, or cache them locally or proxy serve them locally. HTH.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by MrQuincle on Friday December 09, 2016 @06:31AM (#13138127)
Sounds like a perfect CDN opportunity. This doesn't exist yet?

Something like:

https://user.imagecdn.io/website/image

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by tantalor on Thursday December 08, 2016 @10:12PM (#13136389)
Who cares about warnings? Do your users browse with devtools open?

At worst the users see the grey "i" in circle icon: https://googlesamples.github.io/web-fundamentals/fundamental...

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by bjacobel on Thursday December 08, 2016 @10:23PM (#13136436)
A single HTTP request in an otherwise HTTPS page can compromise the privacy and integrity of a user's connection. SSL/TLS isn't just about checking all the boxes so Chrome will give you the prettier icon, there are real stakes for users.
Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by andrewmunsell on Thursday December 08, 2016 @11:07PM (#13136592)
To expand on this--

Imagine you have a website with a payment form on an HTTPS page, but you embed some external analytics script over HTTP. If your visitor's request is MITMed (e.g. they're in a coffee shop or some other insecure WiFi access point, etc), then an attacker can modify the script (that's over HTTP) to send these credit card details to the attacker's server. Once there's a single HTTP resource on the page, HTTPS means a whole lot less, hence the scary warnings.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by baybal2 on Friday December 09, 2016 @10:55AM (#13139414)
>Once there's a single HTTP resource on the page, HTTPS means a whole lot less, hence the scary warnings.

More like if there is a single line of 3rd party code.

Re:Chrome 56 Beta: “Not Secure” Warning, Web Bluetooth, and ... by kuschku on Friday December 09, 2016 @04:59AM (#13137795)
No, they see a yellow warning icon instead of the green https, and in some browsers the https is even red, and strikethrough.

That's quite concerning as far as warning signs go.

And I don't want to have to compromise the users safety by switching entirely back to HTTP, which would just give no warning.