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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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

Closed (moved)
Open
Opened Dec 04, 2011 by Robert Ransom@rransom

Proposal 171 changes broke ‘tor2web mode’

A ‘git bisect’ traced the problem to the proposal 171 changes, and then to commit e8b9815711e7cd1ef0b83153aefcc0d05e817f4e.

This commit causes circuit_has_opened to send two ESTABLISH_RENDEZVOUS cells on each rendezvous circuit, because connection_ap_attach_pending can never attach a stream to a CIRCUIT_PURPOSE_C_ESTABLISH_REND circuit. ‘wanoskarnet’ says that hidden service client support seemed to still be working in non-tor2web-mode versions of 0.2.3.x because they cannibalized pre-built three-hop circuits, and circuit_has_opened is never called for those.

This is also the cause of #4171 (moved) (wanoskarnet diagnosed this, too).

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