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

Re: [tor-bugs] #13192 [Tor]: Collect aggregate stats of total hidden service usage vs total exit usage in Tor network

#13192: Collect aggregate stats of total hidden service usage vs total exit usage
in Tor network
-----------------------------+---------------------------------
     Reporter:  arma         |      Owner:
         Type:  enhancement  |     Status:  needs_review
     Priority:  normal       |  Milestone:  Tor: 0.2.???
    Component:  Tor          |    Version:
   Resolution:               |   Keywords:  SponsorR, tor-relay
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+---------------------------------

Comment (by dgoulet):

 Replying to [comment:19 karsten]:
 > Regarding overflow, I think we'd be in trouble after 1 TiB, because
 we're casting the unsigned long into signed long for adding noise.  That's
 1 TiB/day or 12.7 MB/s on average.  We could switch to int64_t.  It's just
 32 more bits per relay.  And we'll need a new set of obfuscation
 functions.  Should we do that?

 I would definitely go for uint64_t/int64_t here, it's pretty cheap memory
 wise and can prevent issues that we think are improbable now but are the
 next day :).

 >
 > The log statement you refer to is in the "CLASSIFIED" commit that's only
 there for debugging purposes and that should go away before we give out
 the branch to relay operators.  Unless you found another log statement in
 the other commits?

 Sorry for that, I'll know next time that CLASSIFIED means will disapear :)

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