News for hackers. Stuff that matters.
Re:HTTPS for GitHub Pages by MichaelGG on Wednesday June 08, 2016 @10:38PM (#11867217)
How do you do that in CloudFlare? I didn't know you could change the host in non-enterprise versions. All I've seen is the ability to proxy request to a specific IP or CNAME.

If you CNAME your site to foo.github.com, it doesn't change the R-URI or Host header.

Re:HTTPS for GitHub Pages by 2bitencryption on Thursday June 09, 2016 @02:35AM (#11867895)
Re:HTTPS for GitHub Pages by MichaelGG on Thursday June 09, 2016 @04:10AM (#11868163)
That article doesn't address what I said at all. That's showing how to disable encryption on the backend (CF to Github) by selecting "Flexible".

Looking at CF's help again and having used them a bit, there seems to be no way at all to enable full encryption (user-CF-github) with CF's non-enterprise offerings. This is because the request from CF to Github is still requested with your domain name (TLS and host header).

In order for it to work with Github's *.github.io cert, Cloudflare would need to offer an option to rewrite the request itself, not just proxy it.

Re:HTTPS for GitHub Pages by manigandham on Thursday June 09, 2016 @04:25AM (#11868203)
You're right that the host header wouldn't match but Cloudflare has an option to enable SSL to origin without checking for completely validated certificate. They call this Full rather than Strict: https://www.cloudflare.com/a/static/images/ssl/ssl.png

So you can still get an encrypted connection without a verified certificate.

Re:HTTPS for GitHub Pages by MichaelGG on Thursday June 09, 2016 @06:19AM (#11868474)
>encrypted connection without a verified certificate

Encryption doesn't work very well without authentication. In most cases any attacker with access to the medium has read+write. And without auth, you only need to, say, change DNS to insert yourself.

Opportunistic encryption is really just a last-line defence against dragnet type surveillance. Which is good, but it's hardly having end-to-end.