[tor-bugs] #1926 [Metrics]: Extra-info descriptors have corrupt {write, read}-history lines

[Tor Bug Tracker & Wiki]

#1926: Extra-info descriptors have corrupt {write,read}-history lines
---------------------+------------------------------------------------------
 Reporter:  karsten  |       Owner:  karsten
     Type:  defect   |      Status:  new    
 Priority:  normal   |   Milestone:         
Component:  Metrics  |     Version:         
 Keywords:           |      Parent:         
---------------------+------------------------------------------------------

Comment(by karsten):

 I had a closer look at the archives and found more mysteries. I think
 there's a bug in the byte counting code or in the state loading code. But
 staring at the code for two hours didn't help me find the bug. Maybe
 someone else is more lucky?

 Here's my analysis so far:

 - Affected versions range from 0.2.0.23-rc to 0.2.2.13-alpha, so it's an
 old bug. The bug might even be older than 0.2.0.x when relays wrote their
 history lines to their server descriptors which I didn't look at.

 - Both relays on Windows and Linux are affected. I didn't find other
 platforms, but I expect the bug to affect all platforms.

 - Reported write-history and read-history lines have dates both in the
 past (see attached file past) and in the future (see attached file
 future.bz2). I found timestamps 1970-01-02 and 1985-06-11 as well as
 2020-08-01 and 2028-09-23.

 - For timestamps in the future, relays keep reporting the same history
 lines over and over again. We have a relay reporting the same bandwidth
 history ending on 2009-08-12 for two years between 2007-08-15 and
 2009-07-11.

 Someone willing to win the oldest bug prize? :)

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