[Users] [Bug 4170] Problem accessing RSS feeds for sites using Cloudflare with TOR proxy

noreply at thewildbeast.co.uk noreply at thewildbeast.co.uk
Wed Oct 2 15:54:45 CET 2019


https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4170

--- Comment #5 from Santa Claws <bugreporter at riseup.net> ---
This is an issue which many Tor users have faced, not just those of Claws Mail.

I will not use the URL provided by the original reporter because Scott Helme is
known to additionally strengthen his headers, so perhaps not a good example and
here is another one.

The symptom seems to be the captcha:

$ curl -s --socks5-hostname 127.0.0.1:9050 https://www.pine64.org/feed/ | grep
-i "<title>.*</title>" | head -n 1

<title>Attention Required! | Cloudflare</title>


An in-depth direct discussion with Cloudflare was shared on GitHub:

https://github.com/Eloston/ungoogled-chromium/issues/783

where someone shared a simple solution:

https://github.com/Eloston/ungoogled-chromium/issues/783#issuecomment-536205751

through the command:

curl --http2 -A "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101
Firefox/60.0" -v --socks5-hostname 127.0.0.1:9050 --max-redirs 0 --tls-max 1.2
--ciphers ECDHE-ECDSA-AES128-GCM-SHA256 <URI>

Testing this shows that the actual solution is to specify explicitly the
ciphers (--ciphers) which Cloudflare supports (can be checked on SSL Labs for
the host) and a popular user agent ("Mozilla..."). So:

$ curl -s --http2 -A "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101
Firefox/60.0" --socks5-hostname 127.0.0.1:9050 --ciphers
ECDHE-ECDSA-AES128-GCM-SHA256 https://www.pine64.org/feed/ | grep -i
"<title>.*</title>" | head -n 1

        <title>PINE64</title>

This obviously solves the issue.

The actual solution is simple: give an option to the users to specify per-feed
specific curl options. So this is a valid feature request which may solve both
this issue and bug#4184.

Andrej,

I see no option to reopen this (at least with JS disabled). Please reopen and
comment to confirm.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Users mailing list