[tor-bugs] #6676 [Tor]: Nuke ‘MyFamily’

[Tor Bug Tracker & Wiki]

#6676: Nuke ‘MyFamily’
-------------------------+--------------------------------------
     Reporter:  rransom  |      Owner:
         Type:  task     |     Status:  assigned
     Priority:  major    |  Milestone:  Tor: 0.2.7.x-final
    Component:  Tor      |    Version:
   Resolution:           |   Keywords:  tor-relay needs-proposal
Actual Points:           |  Parent ID:  #15060
       Points:           |
-------------------------+--------------------------------------

Comment (by cypherpunks):

 I believe it is dangerous to use all 3 relays in a circuit from a single
 entity - even if the entity is acting honestly.

 MyFamily is hated and not properly used because:
 1) it is cumbersome to manage
 2) there are no incentives for a relay operator to set it properly
 3) it was not easy to verify whether MyFamily was setup correctly on all
 your relays

 1) I'm aiming to make it very easy for relay operators to manage MyFamily
 without them even knowing what MyFamily is (using an ansible role
 https://github.com/nusenu/ansible-relayor)
 2) create a tor operator "bandwidth ranking" based on the family (new
 compass group-by family functionality). So a relay operator that wants to
 move up on the list has a reason to properly set MyFamily (using provided
 tools or manually). MyFamily is currently even the only way to properly
 group relays of a certain operator toghether. Using contactInfo is a much
 weaker since it does not require any mutual agreement.
 3) relay operators can use compass to very easily verify whether their
 MyFamily is setup correctly using the Family lookup (which is already
 available today)

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