5 ms·
My jekyll based static site hosted on Github Pages uses cloudflare for https. Saying that my site is compromised by CloudBleed is a bit too much. http://www.do
by manojlds 10y ago
My jekyll based static site hosted on Github Pages uses cloudflare for https. Saying that my site is compromised by CloudBleed is a bit too much.
http://www.doesitusecloudflare.com/?url=www.stacktoheap.com http://www.doesitusecloudflare.com/?url=www.stacktoheap.com
- arianvanp 10y agoBut it is compromised.... this is literally the only use case in which you can get comprimised. If you put your _http_ page behind cloudlfare https
- blibble 10y agoif it's public static content what exactly has been compromised?
- mcbits 10y agoIP addresses of visitors? Depending on the site or visitor, that could be theoretically a compromise. But the parent comment is untrue. Cloudflare will have unencrypted data in memory at some point, even if it's encrypted coming and going. This is how they eliminate the scary browser message about self-signed certificates, ironically.
- bpicolo 10y agoThey have a (more expensive) version that encrypts all the way to your own edge.
- gkya 10y agoWell it probably just checks if the given domain uses CloudFlare and reports compromised if positive.
- GrinningFool 10y agoChances are it is. The difference being that the leaked data in your case could not have been sensitive.