The Mozilla auto_config database requires an unusable CAPTCHA for Torified requests
I’ve noticed that the Mozilla configuration database (https://live.mozillamessaging.com/autoconfig/v1.1/) often presents a CAPTCHA when the request originates from Tor so the
fetchFromISO method fails. We should ask if Mozilla can be more Tor-friendly.
That CAPTCHA is not displayed in the GUI so the user cannot do anything about it.
#3 Updated by anonym 2018-03-13 21:25:04
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 40
Good news! I managed to solve it by making said HTTP fetch respect
general.useragent.override. Presumably this is just Cloudflare’s (which is the cause of this CAPTCHA (surprise!)) usual scrutiny of everything originating from the Tor network.
What remains is to make TorBirdy set the pref accordingly (currently it sets it to the empty string, which actually is part of causing this problem).
#12 Updated by anonym 2019-02-13 15:06:17
- Status changed from In Progress to Rejected
- Assignee deleted (
- % Done changed from 40 to 0
> Good news! I managed to solve it by making said HTTP fetch respect
Turns out I was wrong; “said HTTP fetch” already respected that pref (my fix would only insist on it an extra time :)). This casts doubt over all my conclusions for this issue, which I think was temporary for whatever reason. I cannot reproduce, no matter the useragent string or whatever. Rejecting.