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

Re: [tor-bugs] #1796 [Tor - Relay]: write-history and read-history in extra-infos leaks the relay's used bandwith if the bandwidth limit is changed

#1796: write-history and read-history in extra-infos leaks the relay's used
bandwith if the bandwidth limit is changed
------------------------------+---------------------------------------------
 Reporter:  lancelot666       |        Type:  defect                    
   Status:  new               |    Priority:  minor                     
Milestone:                    |   Component:  Tor - Relay               
  Version:  Tor: unspecified  |    Keywords:  write-history read-history
   Parent:                    |  
------------------------------+---------------------------------------------

Comment(by lancelot666):

 The maximum reported bandwidth depends on the RelayBandwithRate:

 From rephist.c (List 1574)

 if (options->RelayBandwidthRate ){
   cutoff = options->RelayBandwidthRate * NUM_SECS_BW_SUM_INTERVAL;
 } else{
   cutoff = UINT64_MAX;
 }
 ...
 if (total > cutoff) total = cutoff;

 I don't know how to describe it in a different way :/. By cutting only
 with the current value and not the old value previously stated in the
 config file, one leaks some information one might want to hide. I'm not
 sure, but the Bug #516 (fixed) mentioned a similar problem.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1796#comment:2>
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