[tor-bugs] #2708 [Tor Client]: Tor chooses at most one entry guard per family

[Tor Bug Tracker & Wiki]

#2708: Tor chooses at most one entry guard per family
------------------------+---------------------------------------------------
 Reporter:  arma        |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  normal      |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------

Comment(by arma):

 Replying to [ticket:2708 arma]:
 > That routerlist_add_family() line means that we do not consider any
 nodes to be a new guard if they're in the family of one of our current
 guards.
 >
 > Is that a good idea (due to increased diversity)?

 After writing
 https://blog.torproject.org/blog/research-problem-better-guard-rotation-
 parameters I feel more strongly that this choice was (is) a good idea. If
 all your guards are controlled by the same person they can influence your
 path more easily, e.g. by the denial-of-service-denial-of-anonymity
 attacks.

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