11–20 of 63 posts
Cloudflare is a valid suggestion, albeit (IMO) inferior to letsencrypt in many cases. Surprised to not see it mentioned here, given that it also costs nothing, for arguably more security.
Not to mention that Cloudflare has no tolerance for mocking murdered female protestors. One little article and they kill your site with no warning.
Cloudflare is a valid suggestion, albeit (IMO) inferior to letsencrypt in many cases. Surprised to not see it mentioned here, given that it also costs nothing, for arguably more security.
LE doesn't work here. As the fine article points out, GitHub Pages does not support TLS on custom domains. With CF, this works. For the sort of thing that you'd host on GHP, this is totally fine in my opinion. In fact, because CF is a pretty good CDN it likely accelerates page load times considerably for Non-Americans. (I wish it'd be possible to do something similar for readthedocs, which only has one origin and it'…
edit : I also use letsencrypt certificates on my Linodes.
Get SSL from using a thirdparty MITM? Not only do they control your DNS they also control all traffic going to your site, also the connection between you and them is not encrypted. I figured this would be a tutorial for letsencrypt. Cloudflare certainly is an option but it's not one I would recommend for -most- people unless I know why they're opting for SSL. If it's static content then sure- but I don't support clou…
> also the connection between you and them is not encrypted. The tutorial uses the Full encryption option, which does encrypt the data between your origin server and Cloudflare. You might be thinking of their flexible SSL option? [EDIT] I might add that for anyone not using GitHub Pages as per the tutorial, they'll need additional steps to get Full SSL working with Cloudflare. It's not effortless.
I brought this up and was told "This is something we are definitely considering." but heard nothing beyond that.
FYI there is an alternative to Github Pages + Cloudflare if you want to use Let's Encrypt using the same features of Github Pages: Gitlab Pages. It allows you to add your own certificates with the only downside that there is no good option to enforce HTTPS (only workarounds, at least for now; there is a discussion on the matter [1]), if this is a problem for you the solution is (Github|Gitlab|Bitbucket)+Netlify, whic…
You also have to use GitLab.
Earlier quoted context omitted.
> also the connection between you and them is not encrypted. The tutorial uses the Full encryption option, which does encrypt the data between your origin server and Cloudflare. You might be thinking of their flexible SSL option? [EDIT] I might add that for anyone not using GitHub Pages as per the tutorial, they'll need additional steps to get Full SSL working with Cloudflare. It's not effortless.
The problem is CloudFlare offers zero way for an end user to identify if a site is setup with flexible SSL or not. Therefore I have no way of verifying the full path back to the origin. I brought this up and was told "This is something we are definitely considering." but heard nothing beyond that.
by offering the "flexible ssl" option at all it seems that they couldn't give a toss whether on not it actually protects anyone
Get SSL from using a thirdparty MITM? Not only do they control your DNS they also control all traffic going to your site, also the connection between you and them is not encrypted. I figured this would be a tutorial for letsencrypt. Cloudflare certainly is an option but it's not one I would recommend for -most- people unless I know why they're opting for SSL. If it's static content then sure- but I don't support clou…
Playing Devil's advocate: when you run your site on any provider, except maybe colo'ing, you're also giving them access to that data, as they could peek into the system's memory . Using Cloudflare is just adding a second provider.
FYI there is an alternative to Github Pages + Cloudflare if you want to use Let's Encrypt using the same features of Github Pages: Gitlab Pages. It allows you to add your own certificates with the only downside that there is no good option to enforce HTTPS (only workarounds, at least for now; there is a discussion on the matter [1]), if this is a problem for you the solution is (Github|Gitlab|Bitbucket)+Netlify, whic…
> the only downside [is] that there is no good option to enforce HTTPS You also have to use GitLab.
FYI there is an alternative to Github Pages + Cloudflare if you want to use Let's Encrypt using the same features of Github Pages: Gitlab Pages. It allows you to add your own certificates with the only downside that there is no good option to enforce HTTPS (only workarounds, at least for now; there is a discussion on the matter [1]), if this is a problem for you the solution is (Github|Gitlab|Bitbucket)+Netlify, whic…
> the only downside [is] that there is no good option to enforce HTTPS You also have to use GitLab.