News for hackers. Stuff that matters.
Re:HTTPS for GitHub Pages by avyfain on Wednesday June 08, 2016 @04:25PM (#11865363)
"HTTPS is not supported for GitHub Pages using custom domains"[1] which is annoying.

[1]: https://help.github.com/articles/securing-your-github-pages-...

Re:HTTPS for GitHub Pages by rev_bird on Wednesday June 08, 2016 @08:44PM (#11866824)
Custom domains would be huge for me, but I totally understand. How would they ever manage to do it? They'd either need a zillion separate entries, or the broadest wildcard cert ever.
Re:HTTPS for GitHub Pages by nsgi on Thursday June 09, 2016 @06:33AM (#11868515)
Lots of certificates with 100 hostnames each is how CloudFlare does it.
Re:HTTPS for GitHub Pages by oakwhiz on Thursday June 09, 2016 @01:59AM (#11867801)
Let's Encrypt?
Re:HTTPS for GitHub Pages by MichaelGG on Wednesday June 08, 2016 @10:45PM (#11867243)
Separate entries in what? Computers do pretty good at handling many "entries". TLS will indicate the host so they can send the right cert back.
Re:HTTPS for GitHub Pages by rev_bird on Thursday June 09, 2016 @04:09PM (#11871973)
Sorry, I meant in an Apache config file or something.
Re:HTTPS for GitHub Pages by libeclipse on Thursday June 09, 2016 @05:00AM (#11868276)
Or they could let users specify their own certs.
Re:HTTPS for GitHub Pages by konklone on Friday June 10, 2016 @12:12PM (#11877427)
Wordpress did this by issuing Let's Encrypt certs on demand for every domain people CNAME their way.
Re:HTTPS for GitHub Pages by 2bitencryption on Thursday June 09, 2016 @02:31AM (#11867888)
I just set up HTTPS in ten minutes using a free cloudflare account and github pages with my custom domain. You do kind of add the middleman of Cloudflare, but I'm totally okay with that.