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

Closed (moved)
Open
Opened Jun 14, 2012 by Nick Mathewson@nickm🐙

Possible assertion failure in connection_ap_handshake_attach_circuit()

Vektor reports that an AdvOR user reported a failure of the assertion

tor_assert(introcirc->_base.purpose ==  CIRCUIT_PURPOSE_C_INTRODUCING); 

in connection_ap_handshake_attach_circuit().

His fix is to replace the test in circuit_is_acceptable() so that CIRCUIT_PURPOSE_C_INTRODUCE_ACK_WAIT circuits can no longer get returned.

We should investigate. Filing for 0.2.2 since ISTR that's what AdvOR is tracking.

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