[tor-bugs] #5053 [Tor]: Fix IPv6 implementation for bridge statistics

[Tor Bug Tracker & Wiki]

#5053: Fix IPv6 implementation for bridge statistics
-----------------------------+----------------------------------------------
 Reporter:  karsten          |          Owner:  ln5               
     Type:  enhancement      |         Status:  needs_revision    
 Priority:  major            |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor              |        Version:                    
 Keywords:  ipv6 tor-bridge  |         Parent:                    
   Points:                   |   Actualpoints:                    
-----------------------------+----------------------------------------------
Changes (by nickm):

  * status:  needs_review => needs_revision


Comment:

 okay, I'll try to review the whole branch here...

 Stuff we could fix after merge:
  * The duplicated code in the new geoip*ipv6() functions is scary. Gotta
 refactor that out.  Cut-and-pasting in programming is begging for bloat
 and bugs.
  * Passing in6_addr by value? it is a 16-byte structure; that kind of
 thing one usually passes by reference.
  * Comparing in6_addrs with memcmp is iffy; there's no guarantee that they
 can't contain padding or uninitialized fields. If we're going to use
 memcmp, we should probably be comparing  the s8_addr fields.
  * The comment that says that the in6_addrs are in "host order" seems
 wrong.
  * The comment /* No alignment issue here, since _key really is a pointer
 to uint32_t */ seems wrong.
  * The clear_geoip_db(); that got removed from geoip_load_file() : where
 did it go?  It looks like we just removed it entirely, which means that
 reloading a geoip file will wind up with entries both from the old file
 and the new one.  That's a big bug.
  * Gotta fix all the XXX5053; are there any left?

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