Opened 8 years ago

Last modified 3 years ago

#7457 new enhancement

Add client-side log indicator that an obfsbridge works

Reported by: asn Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-client, pt, tor-bridge, easy, usability, sponsor8-maybe
Cc: isis Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Bridge operators can be reasonably sure that obfsproxy works for them since they see the Registered server transport log message.

OTOH, clients can't be sure whether their obfsproxy works or whether they connected to a bridge with obfsproxy.

I think we should add PT information to one of the "connected to bridge" log messages.

Specifically, to:

log_notice(LD_DIR, "Learned fingerprint %s for bridge %s"

or to

log_notice(LD_DIR, "new bridge descriptor '%s' (%s): %s"

IIUC the latter will appear in the logs everytime we connect to a bridge, even if we knew the bridge fingerprint.

Child Tickets

Change History (7)

comment:1 Changed 8 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

Bumping to 0.2.5, along with other remaining noncritical enhancements.

comment:2 Changed 7 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:3 Changed 5 years ago by isis

Cc: isis added
Keywords: tor-bridge added
Priority: normalminor

This could possibly be fixed at the same time that we do #17193? It's the same lines of code, at least.

comment:4 Changed 4 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:5 Changed 4 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:6 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:7 Changed 3 years ago by nickm

Keywords: easy usability sponsor8-maybe added
Severity: Normal
Note: See TracTickets for help on using tickets.