Re: [tor-bugs] #32864 [Community/Relays]: Reproduce Arthur's exit failures and then contact or badexit the relays

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#32864: Reproduce Arthur's exit failures and then contact or badexit the relays
-------------------------------------------------+-------------------------
 Reporter:  arma                                 |          Owner:  gk
     Type:  enhancement                          |         Status:
                                                 |  needs_review
 Priority:  Medium                               |      Milestone:
Component:  Community/Relays                     |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  network-health, network-health-      |  Actual Points:
  roadmap-2020Q1, GeorgKoppen202003              |
Parent ID:                                       |         Points:  2
 Reviewer:  dgoulet                              |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by gk):

 * status:  assigned => needs_review
 * reviewer:   => dgoulet


Comment:

 Okay, some final note here: I created [https://gitlab.torproject.org/gk
 /helper-scripts/-/commit/b40a0e100e8d3e6d1503076ddb6ddfbf05346a59 a
 script] that pulls exit relays failing DNS queries with a certain
 threshold (by default only relays failing 10/10 times are shown) out of
 some JSON blob created either by Arthur's exit dns check tool or by my own
 run. I contacted the respective exit relay ops (that's the "[s]" below
 where "[sf]" means "mails sent but bounced") last week and did not really
 hear back (just one replied looking into it). So, now's the time to
 actually start the badexiting process. I pushed a rule to mark all the
 exits below as badexit:
 {{{
 [s]
 "$296B2178FD742AB35AB20C9ADF04D5DFD3D407EB"
 [s]
 "$3BADB3EFFB87534736BFAC9A2024AB78401BDBC3"
 [no email address]
 "$4684E03631097C77F013637EC800D499CD71C250"
 [s]
 "$51AE5656C81CD417479253A6363A123A007A2233"
 [no email address]
 "$53FF368902D124FA9A806D149AF22C3A6357B150"
 [s]
 "$5AD1D535373C05BB1624BD2A76DDE713E974240E"
 [s]
 "$9AD12F0E3CC871D59ACA14BB4076CDD8CB28DE57"
 [s]
 "$9C339F4F3101B744C8C040C9F51D63B520D38712"
 [sf]
 "$9E9C2223EA179F52BA73A24BFDE2E44DCA468EEF"
 [no email address]
 "$A5B682E846615088362A3B2BD11C353C84778659"
 [s]
 "$AD1639F47D6233E812A67F98F9D76FF55D1D2ECC"
 [no email address]
 "$F912C0A30DC9CBD4E7BA566C235DA194C4623EC0"
 [s]
 "$FAD823A2AA7400D4A8107D7CD83050EEBB7A51FE"
 [no email address]
 "$FBBC3BD58B471F6227DC0F05265C6A37C770905F"
 [s]
 "$FE59C12C9697E742CD3F7ADBAF6385EA1C8B379F"
 }}}
 (FWIW: As said previously I slightly modified arthur's to use
 `https://eff.org` to check for exits as the results compared with Arthur's
 allow us to differentiate between DNSSEC only issues and more general
 ones. That's useful when contacting relay ops in particular until #33179
 is solved).

 Marking this ticket as in `needs_review` for the script I want to add to
 the `helper-scripts` repo.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32864#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs