[tor-relays] Exit relay operators please help test #2667 branch

[Chris Dagdigian]

Have a tor exit running in the US ; fingerprint is 
3DE567C1350C0E858C6147AECB06EA9B3EAF3261 and OR address is 
71.174.105.126:9001

Just built and launched the ticket-2667 branch; came up as:

[notice] Tor 0.4.6.0-alpha-dev running on Linux with Libevent 
2.0.21-stable, OpenSSL 1.0.1t, Zlib 1.2.8, Liblzma N/A, Libzstd N/A and 
Glibc 2.19 as libc.

I'll monitor the log notices but feel free to probe to test. Thanks!




> Roger Dingledine <mailto:arma at torproject.org>
> January 28, 2021 at 1:40 AM
> Hello friendly relay operators,
>
> Another day, another weird thing with the Tor network. This time we
> have some jerk bombing the directory authorities with directory fetches,
> and doing it via exits:
> https://lists.torproject.org/pipermail/network-health/2021-January/000661.html
>
> The network is mostly holding together, but I wouldn't say it is pretty.
>
> One of the long-term fixes will be ticket #2667:
> https://gitlab.torproject.org/tpo/core/tor/-/issues/2667
> where exit relays refuse to let users connect back into the Tor network.
>
> David and I made a branch this evening that implements #2667, and it
> could use some testing. If you're comfortable building your exit relay
> from a git branch, please do, and let us know how it goes. It is the
> "ticket2667" branch on either
> https://git.torproject.org/user/arma/tor
> or
> https://gitlab.torproject.org/arma/tor/
>
> And if your relay is currently using 100% cpu and/or way more bandwidth
> than usual, you might be especially excited to try out this patch. :)
>
> When the defense triggers, you will see an info-level log line like
> "%s tried to connect back to a known relay address. Closing."
> (where %s is the destination, so don't get upset at them. :)
>
> You can let us know how it's going either by mail just to me, or by a
> reply on the list, whichever you prefer. Once we know that you're running
> the branch, we can also probe your relay remotely to verify that it is
> correctly refusing those connections.
>
> Thanks!
> --Roger
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20210128/4081b8b5/attachment.htm>