Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,066
    • Issues 1,066
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • 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.

  • The Tor Project
  • Core
  • Tor
  • Issues
  • #11397

Closed
Open
Opened Apr 03, 2014 by Trac@tracbot

Keep using too-dirty circuits if no new circuit can be built?

When behind a firewall that not only lets only a few ports through but that also validates that only the expected protocol is passing through, it may take dozens of seconds to build a new circuit. In the meantime, new connections will timeout before new circuits are built.

This behavior deserves some attention. Perhaps until a new circuit is built, an old circuit should continue to be used or after a few seconds of waiting for the new circuit.

However, if there's no connection alive, there might not even be old circuits to fall back to. Then, the user might be given the choice to always keep an old circuit open, even if idle, until a new circuit is built.

Trac:
Username: evandro

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/core/tor#11397