Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 313
    • Issues 313
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #7457
Closed
Open
Created Nov 12, 2012 by George Kadianakis@asnContributor

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
Time tracking