Opened 4 years ago

Last modified 4 years ago

#18165 new enhancement

Scripts to determine vote divergence

Reported by: micah Owned by:
Priority: Medium Milestone:
Component: Core Tor/DirAuth Version:
Severity: Normal Keywords: dirauth, consensus, votes
Cc: atagar, dgoulet Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We need to find a way to determine vote divergence so we can find out who is and who is not voting on things that everyone else is agreeing on.

DocTor is the perfect framework for monitoring everything, so we need to somehow link those things (or parse each DirAuth vote to find divergences? I dont know if Reject lines are published in the votes, I know Invalid and BadExit are there, but I dont think Reject is, perhaps that is because if it were there it would leak that information?)

If we have a convenient way to see which DAs are not voting to reject relays, then we can use that to notify and apply appropriate social pressure to get them to block things.

Damien, do you have some thoughts about how we could do this with DocTor?

Child Tickets

Change History (1)

comment:1 Changed 4 years ago by micah

Another reason why this would be important... A few days ago longclaw had a set of relays added to its config to reject. The configs were made correctly, and the daemon was hupped through the standard process.

Today, while looking at longclaw's votes, I noticed that the AuthDirReject lines that were in the config were not working, the relays were still being voted on! I don't know why, but silent fail of the dirauth loading rules is not a good thing.

I stopped the tor process completely, and then started it again, and then in the next vote, the relays were no longer there.

It would have been *really* good to know that these were not there, when I thought that they were. I just happened to notice that they were not there by manually parsing the votes

Note: See TracTickets for help on using tickets.