News for hackers. Stuff that matters.

A comment on Chrome 68 will mark all HTTP sites as “not secure”. Parent comment

Re:Chrome 68 will mark all HTTP sites as “not secure” by _asummers on Thursday February 08, 2018 @02:19PM (#16334737)
If you have a simple static site, you can have Google's Firebase hosting thing do the HTTPS for you, without management, for free. Netlify[1] is another one I see recommended around here decently often which has the same service.

[0] https://firebase.google.com/docs/hosting/

[1] https://www.netlify.com/docs/ssl/

[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by josteink on Thursday February 08, 2018 @03:58PM (#16335548)
So the solution to Google having too much power, is using and depending on Google for more things?

Really?

[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by ukoki on Friday February 09, 2018 @10:42AM (#16340957)
or use cloudflare

https://www.cloudflare.com/ssl/

[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by kalleboo on Thursday February 08, 2018 @10:31PM (#16337711)
Amazon also issue/autorenew free certs for AWS customers (so you can set–and-forget an HTTPS site on CloudFront)

https://aws.amazon.com/certificate-manager/

[ Parent | on HN ]