[tor-bugs] #9199 [BridgeDB]: Rethink the logging of BridgeDB

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Jul 3 15:00:55 UTC 2013

#9199: Rethink the logging of BridgeDB
 Reporter:  asn       |          Owner:     
     Type:  task      |         Status:  new
 Priority:  normal    |      Milestone:     
Component:  BridgeDB  |        Version:     
 Keywords:            |         Parent:     
   Points:            |   Actualpoints:     
 Now that we are playing around with BridgeDB, it's probably a good idea to
 also improve its logging.

 For example, BridgeDB currently doesn't have any debug logs during
 descriptor parsing (which made it harder to find the root of #9174).

 Also, we should make sure that BridgeDB can scrub client's IPs from the
 logs (even for debug logs). Example of offending logs:
   Valid recaptcha from <IP>...
   [DEBUG] getBridgesForIP(<IP>, ...)

 Also, maybe we should consider using Tor's extended nicknames to improve
 log greppability. Extended nicknames combine the identity digest and the
 nickname of a router in the same line. Example:

 Check Tor's function `node_get_verbose_nickname()` and

 We should also identify other information that the BridgeDB operator would
 be interested in and log them (maybe even write a heartbeat log with

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9199>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

More information about the tor-bugs mailing list