Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #7457

Closed (moved)
Open
Opened Nov 12, 2012 by George Kadianakis@asn

Add client-side log indicator that an obfsbridge works

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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#7457