News for hackers. Stuff that matters.
Re:Chrome 56 will mark HTTP pages with password fields as no... by ycitm on Sunday January 22, 2017 @05:18PM (#13457944)
If you have control of your nameservers you can use cloudflare's free TLS offering and keep your current webhost.
Re:Chrome 56 will mark HTTP pages with password fields as no... by slrz on Sunday January 22, 2017 @07:05PM (#13458569)
What about actually solving the problem instead of tricking the user into believing their data is encrypted while being transferred to you?
Re:Chrome 56 will mark HTTP pages with password fields as no... by andybak on Sunday January 22, 2017 @06:09PM (#13458224)
I'm personally in favour of Cloudflare as the simplest solution - even simpler than letsencrypt. However - there are a few caveats. They tend to hit some countries with a Captcha unless you disable it. Might not be an issue. Their "Flexible SSL is controversial as it only encrypts from client to them - not from them to the server. Personally I think this covers the most obvious threat models and is probably "good enough" for the a lot of use cases.