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 Latty on Sunday January 22, 2017 @06:43PM (#13458440)
Actually, Cloudflare offer you certs they sign (which wouldn't be trusted by others, but they verify), that you can use to encrypt from the server to them. You still have to trust Cloudflare, but it's not plain text from cloudflare to your server.

If you mean the case where you literally can't serve under HTTPS, it's not just getting the cert that is the problem, in most cases running a local proxy of something that will would fix it, although I accept there are cases (cheap shared hosting, I guess) where that's not an option.

[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by jensvdh on Sunday January 22, 2017 @07:31PM (#13458684)
Wouldn't he still have to install the Cloudflare certs on his server then? In that case why not get LetsEncrypt?
[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by Latty on Tuesday January 24, 2017 @06:09AM (#13470448)
In some cases you have the ability to add certs, but not to run the LetsEncrypt software (e.g: shared hosting) - with the short expiry date on LetsEncrypt certs, doing it manually is error-prone.
[ Parent | on HN ]