Re:How to bypass Cloudflare bot protection
by daurnimator on Sunday April 04, 2021 @08:03AM
(#26688785)
A lot of people just verify that X-Forwarded-For matches a Cloudflare-owned IP.
As this post demonstrates, you need to verify against the cloudflare origin pull CA (see https://support.cloudflare.com/hc/en-us/articles/204899617-A... )
Re:How to bypass Cloudflare bot protection
by tgsovlerkhgsel on Sunday April 04, 2021 @11:50AM
(#26690419)
I suspect that the idea here is that XFF is supposed to be trusted, because it is supposed to come from Cloudflare.
Re:How to bypass Cloudflare bot protection
by userbinator on Sunday April 04, 2021 @03:37PM
(#26692202)
For a very long time, XFF-spoofing was a trick to get past journal subscriptions and other paywalls. I don't feel so guilty about disclosing this here now, as a lot of them have (unfortunately) blocked that route. No doubt a few popular bookz/journalz sites owe at least some of their content to this technique. But it's something to try and might still work on a few of them...
Re:How to bypass Cloudflare bot protection
by RiceAndWaters on Wednesday April 07, 2021 @05:25PM
(#26731561)
Hey, I saw one of your past comments where you mentioned being (briefly) active in the bookz scene in the past.
I really want to know more about this scene. If it's not too much work for you, please contact me at [email protected]
Thank you!
X-Forwarded-For should always be treated as forged at least for security purposes (except the hops set by reverse proxies under your control). If you do IP whitelisting based on untrusted X-Forwarded-For you’re doing it terribly wrong.