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 832
    • Issues 832
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • 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
  • #3695

Closed
Open
Created Aug 06, 2011 by Robert Ransom@rransom

Handling of ISO_STREAM is bogus

connection_edge_compatible_with_circuit prevents a stream with ISO_STREAM set from being associated to any circuit to which a stream (not necessarily a different stream) has already been associated. Nothing else looks at ISO_STREAM. (In other news, connection_edge_streams_are_compatible is dead code.)

This treatment of ISO_STREAM should cause excess circuit creation (legacy/trac#3632 (moved)) during anonymous directory operations, and it does not (explicitly) prevent a circuit which has had an ISO_STREAM stream attached to it from having a non-ISO_STREAM stream attached to it later.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking