[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #5608 [Metrics Data Processor]: Order of sanitizing bridge descriptor tarballs matters even though it shouldn't

#5608: Order of sanitizing bridge descriptor tarballs matters even though it
shouldn't
------------------------------------+---------------------------------------
 Reporter:  karsten                 |          Owner:  karsten
     Type:  defect                  |         Status:  new    
 Priority:  normal                  |      Milestone:         
Component:  Metrics Data Processor  |        Version:         
 Keywords:                          |         Parent:         
   Points:                          |   Actualpoints:         
------------------------------------+---------------------------------------
 There's a bug in how metrics-db tries to repair references between bridge
 network statuses, server descriptors, and extra-info descriptors.  In
 theory, the order of processed tarballs shouldn't matter, because we have
 a mapping file with hashed bridge fingerprint, descriptor publication
 time, server descriptor digest, and extra-info digest.  But apparently
 this approach is buggy.  I just tried sanitizing 1 week of tarballs in
 forward and in reverse order.  The result was that sanitized descriptors
 differed.  I suspect the problem is that bridges can publish more than 1
 descriptor in a single second, but I'm not sure yet.  I'm also not sure
 whether this leads to data loss or not.  More analysis required.  We might
 have to sanitize all bridge descriptors again.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5608>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs