From: Jeff King <peff@peff.net>
To: opal hart <opal@wowana.me>
Cc: git@vger.kernel.org
Subject: Re: Cannot access git-scm.com with Tor
Date: Wed, 8 May 2019 19:22:17 -0400 [thread overview]
Message-ID: <20190508232216.GD19990@sigill.intra.peff.net> (raw)
In-Reply-To: <20190508083917.50f2cf59@clamav.local>
On Wed, May 08, 2019 at 08:39:17AM +0000, opal hart wrote:
> On Tue, 7 May 2019 03:33:22 -0400
> Jeff King <peff@peff.net> wrote:
>
> > The "security settings" toggle for the site on Cloudflare is already set
> > to "low", and there are no other restrictions. Is it actually blocking?
> > Or is it asking for a CAPTCHA?
>
> Sorry, it is indeed asking for a CAPTCHA. Google reCAPTCHA does not do
> a great job at accomodating Tor users; it effectively blocks us with an
> endless barrage of puzzles unless we log in to a Google account.
Yeah, even though it at least provides _a_ way to get to the content,
I'd just as soon not inconvenience people for no reason (and in fact,
avoiding CAPTCHAs is why I had initially lowered it from the default).
I dropped the setting in Cloudflare to "essentially off". Using
torbrowser I didn't get a CAPTCHA either before or after the setting, so
I have no idea if it actually changed anything. But hopefully it is
better for you now.
I also checked the settings for git-scm.org (same content, different
domain), which had accidentally been left at "medium". Those are now at
off, too.
-Peff
prev parent reply other threads:[~2019-05-08 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 7:00 Cannot access git-scm.com with Tor opal hart
2019-05-07 7:33 ` Jeff King
2019-05-08 8:39 ` opal hart
2019-05-08 23:22 ` Jeff King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190508232216.GD19990@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=opal@wowana.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).