On 06.07.2016 15:50, Ivan Markin wrote:
The introduction of peering policy definitely solves this issue in a transparent and harmless way. Filed a ticket #19625 [1] to move this discussion there.
On 06.07.2016 14:56, Roger Dingledine wrote:
Speaking of which, a while ago I started a discussion of how to streamline that process: https://trac.torproject.org/projects/tor/ticket/16558
As I see it, removing via directory authority consensus is still the cleaner way, especially in a case of ~100 similar nodes.
What came to my mind was something like a bugtracker for bad nodes.
This way, all node operators can file suspicious nodes to be excluded, which achieves more than blacklisting on their tiny fraction of the network. It would introduce more transparency because relay operators can actually see someone is working on getting a dir auth consensus and get status updates; or at least there is a discussion why there won't be any blocking. Lastly, it would prevent partitioning attacks or similar in contrast to per-node blacklisting.