Re:Life Is About to Get Harder for Websites Without HTTPS
by kiliankoe on Wednesday July 12, 2017 @04:26AM
(#14750983)
I'm using gh pages for my site, on a custom domain. I really don't want to use cloudflare or similar services for personal reasons. Afaict there's not really any other option though :/ I'd love it if GitHub were able to provide me with a LetsEncrypt cert. I've written to them about this before, but they said there was nothing planned yet.
[ Parent
| on HN ]
Re:Life Is About to Get Harder for Websites Without HTTPS
by lucideer on Wednesday July 12, 2017 @08:31AM
(#14751916)
FWIW, I use Gitlab Pages for the same, and they allow you to provide your own cert (be it LetsEncrypt or otherwise). This has become a good bit easier to administer since LE added support for DNS verification, bit you're right, it would be cool to see these providers adding in built LE automated certs.
Re:Life Is About to Get Harder for Websites Without HTTPS
by bikebilly on Wednesday July 12, 2017 @12:53PM
(#14754168)
Thanks for the feedback, there is actually an issue regarding this topic: https://gitlab.com/gitlab-org/gitlab-ce/issues/28996. Feel free to contribute to it!
Re:Life Is About to Get Harder for Websites Without HTTPS
by james-skemp on Wednesday July 12, 2017 @11:35AM
(#14753411)
I've been doing the same. Unfortunately, it seems that if I want to update my cert I have to remove the domain and then add it back in.
Are you aware of a workaround? Otherwise, I agree with the ease now that LE supports DNS verification. I just wish we could edit existing domains in Gitlab.
Re:Life Is About to Get Harder for Websites Without HTTPS
by bikebilly on Wednesday July 12, 2017 @12:54PM
(#14754174)
It's a good point, I just opened an issue about that, feel free to add more context on it: https://gitlab.com/gitlab-org/gitlab-ce/issues/35022