Out of curiosity, what is the need for ensuring a node cannot be put into a family without its consent? What would be wrong with, say, a FamilyName directive? Set the same FamilyName on each node you control, and routes will avoid multiples. On 07/22/2015 03:48 PM, Virgil Griffith wrote: >> Thanks Virgil! > Anytime. > > I don't know the opportunity cost for implementing it, but there's > always proposal #242 ;) > > https://gitweb.torproject.org/torspec.git/tree/proposals/242-better-families.txt > > -V > > On Thu, Jul 23, 2015 at 3:11 AM, Roger Dingledine <arma@xxxxxxx> wrote: >> On Wed, Jul 22, 2015 at 09:31:58PM +0800, Virgil Griffith wrote: >>> I present three graphs of all Tor relays (nodes) with at >>> least one family connection (edge). >> >> Thanks Virgil! >> >> I think the clear first conclusion here is that our current method, >> writing symmetric fingerprints into torrcs, is not consistently easy >> for relay operators to use. >> >> I don't have a fix -- but if anybody out there has been working on a >> proposal for a better design, they should point to these graphs as >> justification that it is a real issue worth solving. >> >> --Roger >> >> _______________________________________________ >> tor-relays mailing list >> tor-relays@xxxxxxxxxxxxxxxxxxxx >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > _______________________________________________ > tor-relays mailing list > tor-relays@xxxxxxxxxxxxxxxxxxxx > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays