News for hackers. Stuff that matters.
Re:HTTPS for GitHub Pages by tvanantwerp on Wednesday June 08, 2016 @03:03PM (#11864696)
Doesn't appear to work with custom domains.
Re:HTTPS for GitHub Pages by travjones on Wednesday June 08, 2016 @03:11PM (#11864768)
Cloudflare's free plan includes one-click SSL for custom domains. That's what I use for my github pages sites.
Re:HTTPS for GitHub Pages by kevincox on Wednesday June 08, 2016 @04:38PM (#11865451)
Although it doesn't validate the backend certificate.
Re:HTTPS for GitHub Pages by jsingleton on Wednesday June 08, 2016 @05:43PM (#11865932)
In some cases it doesn't even connect with TLS due to some connection issue with GitHub / fastly and you need to set it to flexible (no encryption). I wonder if this new forced HTTPS redirect will change/break that?

I haven't quite worked out the rules yet but some GH pages allow full TLS on CF (but not strict cert validation obviously) and some require flexible. I think org pages need flexible (plain HTTP) but project ones support HTTPS (if on a subdomain)?

This update may change all that so will need to experiment again. If it does break things then any new sites after the 15th may not be able to be made to work. If using a CF page rule or HSTS headers to permanently redirect to HTTPS then this could be a problem.

Re:HTTPS for GitHub Pages by Artemis2 on Wednesday June 08, 2016 @06:24PM (#11866163)
If that's what you are talking about, you can select "Full (strict)" in the SSL options to enforce origin certificate validation.

https://support.cloudflare.com/hc/en-us/articles/200170416-W...

Re:HTTPS for GitHub Pages by kevincox on Wednesday June 08, 2016 @06:50PM (#11866315)
But this doesn't work because the backend certificate is invalid (it covers *.github.io rather then example.com).
Re:HTTPS for GitHub Pages by homero on Wednesday June 08, 2016 @08:58PM (#11866873)
But you'd give cf that cname I think
Re:HTTPS for GitHub Pages by kevincox on Wednesday June 08, 2016 @09:20PM (#11866959)
Last time I tested this cloudflare validated using the domain name, not the cname.
Re:HTTPS for GitHub Pages by atonse on Wednesday June 08, 2016 @03:05PM (#11864707)
Probably in the works? SNI should make this pretty easy now, right?

Maybe GH doesn't want the responsibility of hosting everyone's private keys.

Re:HTTPS for GitHub Pages by minimaxir on Wednesday June 08, 2016 @03:05PM (#11864708)
From the documentation:

> HTTPS is not supported for GitHub Pages using custom domains.

Not unsurprising, but unfortunate.

Re:HTTPS for GitHub Pages by tdkl on Wednesday June 08, 2016 @03:46PM (#11865049)
I'm still using kloudsec for this [1] , they presented themselves on HN sometime last year.

[1] https://kloudsec.com/github-pages/new

Re:HTTPS for GitHub Pages by ajhit406 on Wednesday June 08, 2016 @03:45PM (#11865042)
We're working on a static site hosting service called PubStorm (https://www.pubstorm.com) that allows SSL on custom domains. It's free; we're also working on some powerful features that will set it apart from gh-pages.

http://help.pubstorm.com/command-reference/storm-ssl-set/

Re:HTTPS for GitHub Pages by koolba on Wednesday June 08, 2016 @09:23PM (#11866974)
> Doesn't appear to work with custom domains.

Do you have any idea how TLS actually works? If this worked out of the box for custom domains, then GitHub would need to be able to impersonate those domains.

At the very least you'd need a way to upload a private key/cert combo that they could server in response to an SNI request. Given the sheer number of sites that they host (every user effectively has a custom GitHub pages page) that's not really feasible though. Hence only support for *.github.io as that only requires a single wildcard cert.

Re:HTTPS for GitHub Pages by detaro on Wednesday June 08, 2016 @09:32PM (#11867009)
> Do you have any idea how TLS actually works? If this worked out of the box for custom domains, then GitHub would need to be able to impersonate those domains.

If you redirect your domain to my webserver, I can get a certificate for it. E.g. from Let's Encrypt.

Wordpress.com uses that and offers SSL certificates to "million-plus"[0] blogs with custom domains. It's certainly doable at scale, although I totally understand it not having priority for GitHub (esp if it doesn't fit their current technical setup).

[0] https://en.blog.wordpress.com/2016/04/08/https-everywhere-en...

Re:HTTPS for GitHub Pages by davis_m on Wednesday June 08, 2016 @03:04PM (#11864704)
I would hope not. If Github could generate valid SSL certs for random domains, something would be very broken.
Re:HTTPS for GitHub Pages by nileshtrivedi on Wednesday June 08, 2016 @03:27PM (#11864890)
It would just request LetsEncrypt to generate those certs and then prove the "ownership" (more like "control") of those domains by whatever method LetsEncrypt wants (.well-known perhaps?).
Re:HTTPS for GitHub Pages by Nullabillity on Wednesday June 08, 2016 @03:48PM (#11865063)
Yup, .well-known should be pretty simple for them to implement.