News for hackers. Stuff that matters.

A comment on Chrome 56 will mark HTTP pages with password fields as non-secure. Parent comment

Re:Chrome 56 will mark HTTP pages with password fields as no... by robbiewxyz on Sunday January 22, 2017 @05:27PM (#13457990)
I think you could probably just point your DNS at Cloudflare to proxy your site through them; their service includes SSL plus some extras like caching and such for free. I've used them for a handful of projects and it's worked great.
[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by simcop2387 on Sunday January 22, 2017 @05:50PM (#13458120)
That said it will still be insecure because of the unencrypted path from cloudflare to you server but it will hire the error
[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by Latty on Sunday January 22, 2017 @06:39PM (#13458413)
Cloudflare will provide you with certificates they generate, that they verify but won't be accepted by anyone else. (No cost because of that) - this keeps the data secure between you are them. Obviously, you are still trusitng cloudflare in the middle, but still less trust required.
[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by icebraining on Sunday January 22, 2017 @07:36PM (#13458703)
If you can install a certificate, you can already get a real one from Lets Encrypt (you don't actually need to run their client on the server). The problem is that many shared hosting services are still stuck in the past, and don't let you use SSL/TLS at all.
[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by Latty on Tuesday January 24, 2017 @06:11AM (#13470459)
Without running the client, that means manually changing the cert for expiry, which is very short on LetsEncrypt certs. That introudces the possibility of forgetting or messing it up.

I agree that the best option is for shared hosts just to build in support for LetsEncrypt.

[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by Vinnl on Monday January 23, 2017 @10:30AM (#13462820)
Hmm, so let's say I'm hosting my static files on S3. I've currently got CloudFlare setup in front of it but that apparently doesn't help.

Anything I can do other than not using S3?

[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by axman6 on Tuesday January 24, 2017 @02:09AM (#13469413)
Use CloudFront? Took me about an hour to set up for my S3 based blog, free TLS, http/2 and IPv6 without any setup apart from a checkbox.
[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by Vinnl on Thursday January 26, 2017 @02:59AM (#13489569)
Right, so I've currently got CloudFront in front of it, but doesn't that move the problem? Now the connection between CloudFront and S3 is unencrypted.

(I'm probably understanding this wrong, but I'd like to understand why.)

[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by andybak on Sunday January 22, 2017 @06:09PM (#13458225)
For some definitions of "insecure".
[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by andybak on Monday January 23, 2017 @08:06AM (#13461896)
Hmmmm. -4. I fleshed out my thoughts in slightly more detail in another comment: https://news.ycombinator.com/item?id=13458224
[ Parent | on HN ]