[tor-bugs] #9199 [BridgeDB]: Rethink the logging of BridgeDB
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Jul 4 06:23:29 UTC 2013
#9199: Rethink the logging of BridgeDB
----------------------+-----------------------------------------------------
Reporter: asn | Owner:
Type: task | Status: needs_information
Priority: normal | Milestone:
Component: BridgeDB | Version:
Keywords: | Parent:
Points: | Actualpoints:
----------------------+-----------------------------------------------------
Changes (by sysrqb):
* status: new => needs_information
Comment:
Nearly finished with an initial branch. some thoughts/questions:
a) Should we scrub the bridge's fingerprint when safe logging is not
disabled? It can easily be used to retrieve the IP addr via Atlas, etc.
Maybe we should hash the fingerprint by default so various aspects of the
log file are linkable?
b) Using the extended nickname will probably not be in v1 of this patch.
It will be a little invasive to retrieve/store all the info we need.
c) I think providing a heartbeat is a nice idea. How do you feel about
displaying uptime, user GEOIP stats, OS stats (based on user-agent) over
the past n hours? This won't be trivial, but it shouldn't be too
difficult. I think we should push this to v2 also.
d) If we're auditing the logging, do we want to consider switching to
[https://twistedmatrix.com/documents/12.2.0/core/howto/logging.html
twisted.python.log]? Isis brought this up a few weeks ago. If we're going
to make a decision on it, now is a fine
time.[https://twistedmatrix.com/trac/wiki/TwistedLogging 0]
I'm prioritizing some features/enhancements (mainly adding more debug
output and scrubbing) due to the importance of solving #9174. The faster
we are able to fix that, the better.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9199#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list