[tor-bugs] #33182 [Metrics/Consensus Health]: Automate process from reporting bad relays to resolving them as much as possible

Tor Bug Tracker & Wiki blackhole at torproject.org
Thu Feb 27 09:16:02 UTC 2020


#33182: Automate process from reporting bad relays to resolving them as much as
possible
-------------------------------------------------+-------------------------
 Reporter:  gk                                   |          Owner:  gk
     Type:  defect                               |         Status:
                                                 |  needs_review
 Priority:  Medium                               |      Milestone:
Component:  Metrics/Consensus Health             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  GeorgKoppen202002, network-health,   |  Actual Points:  2
  network-health-roadmap-2020Q1                  |
Parent ID:                                       |         Points:  3
 Reviewer:  dgoulet                              |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by gk):

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


Comment:

 Okay, I think I am done here. At least we should have a good starting
 point now dealing with the majority of rejection cases. A patch is up for
 review in my `bug_33182_v2` (https://dip.torproject.org/gk/helper-
 scripts/commit/22e354490abc97e260fb1dd1334212ce6a2aeae5). I've used and
 refined the script during the last couple of bad relay incidents.

 I decided to move the script we use for dealing with bad relays into the
 `helper-scripts` repo for at least two reasons:

 1) It's nothing that has to be sekrit and rather makes it transparent what
 we do when we reject/remove relays
 2) It can use all the helpers in the `helper-scripts` repo (in particular
 all the stem helper infrastructure already built there). Thus, we don't
 need to reinvent the wheel or start using `git submodule`, or doing
 something else which would make things overly complicated.

 dgoulet: with the spirit of that repo and the recent license additions to
 all of your other scripts, I decided to use the same copyright/license
 combo for the `badconf-entry.py` one. I know the original script as under
 the GPL2, so doing what I did hinges on you being okay with that. If you
 feel that's not cool, please speak up, that's fine. I'll make the
 necessary changes. (We are still discussing as a project how to deal with
 treating code we write while working and how to license/copyright that
 one. We are not done here yet, which makes it a bit hard to find an easily
 applicable solution)

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


More information about the tor-bugs mailing list