3 ms·
I was hoping to see something about optional SSL/TLS. I'm even willing to pay for it.
by gabrtv 11y ago
I was hoping to see something about optional SSL/TLS. I'm even willing to pay for it.
- jsingleton 11y agoYou can use CloudFlare with flexible SSL in front of it and set up a page rule to redirect to HTTPS.
- gabrtv 11y agoI had no idea. That's great news!
- drewbug 11y agoBe warned, though: this will only create a secure connection between the user and CloudFlare, not between CloudFlare and GitHub Pages.
- tracker1 11y agoWhile a potential for concern... I would guess that CloudFlare's own routing would take them to an exit node close to Github's... that does make quite a few assumptions though. It would still be more complicated to mitm between CloudFlare and Github than ISP-X (or China) and Github...
- cben 11y agoThere already kinda is TLS on github.io but it's only user<->CDN, CDN<->Github is unencrypted. [https://konklone.com/post/github-pages-now-sorta-supports-https-so-use-it https://konklone.com/post/github-pages-now-sorta-supports-ht...] And it doesn't work on custom domains (Github can't present a cert for your domain); you can make it "work" via Cloudflare but that only works if Cloudflare doesn't validate Github's cert, which introduces yet another unsecure link. [https://github.com/isaacs/github/issues/156 https://github.com/isaacs/github/issues/156]
- cben 11y agoEdit: forgot to say I'm also willing to pay for it.