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
  • #9162

Closed (moved)
Open
Created Jun 28, 2013 by George Kadianakis@asn

get_configured_bridge_by_addr_port_digest() does not work well if digest == NULL

get_configured_bridge_by_addr_port_digest() returns NULL if digest is NULL (the caller doesn't care about the digest) and bridge->identity set.

Normally, the function should return any bridge with addr/port that matches even if it has an identity digest set.

This bug becomes visible when Tor does a second SOCKS request to the pluggable transport proxy after it has learned the identity digest of a bridge. In that second request, the SOCKS arguments are not passed, since digest == NULL but bridge->identity is set.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.5.x-final
Milestone
Tor: 0.2.5.x-final
Assign milestone
Time tracking
None
Due date
None