HTTPS Deployment Growing by Leaps and Bounds

Re:HTTPS Deployment Growing by Leaps and Bounds by seanwilson on Friday December 23, 2016 @02:20PM (#13246674)

I agree with avoiding a VPS when you can. I think e.g. Digital Ocean + Let's Encrypt is just way too low level to be toying with when there's lots of hosting services that let you work at a higher level of abstraction where they deal with all the SSL details for you (e.g. GitHub Pages, Netlify, Heroku).

[ Parent | on HN ]

Re:HTTPS Deployment Growing by Leaps and Bounds by shakna on Friday December 23, 2016 @08:07PM (#13248093)

GitHub Pages doesn't handle SSL for custom domains. The usual workaround is to throw Cloudflare in front of it, but the Cloudflare->GitHub link is still out in the open, and unencrypted.

[ Parent | on HN ]

Re:HTTPS Deployment Growing by Leaps and Bounds by dispose13432 on Saturday December 24, 2016 @09:33PM (#13252581)

>GitHub Pages doesn't handle SSL for custom domains.

That's a problem of GitHub, not of TLS

[ Parent | on HN ]

Re:HTTPS Deployment Growing by Leaps and Bounds by shakna on Sunday December 25, 2016 @07:50AM (#13253957)

Precisely.

[ Parent | on HN ]