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

Closed (moved)
Open
Opened Feb 08, 2013 by bastik@bastik

Introduce MaxCircuitDirtiness per listener

Now that you have such nice isolation features per listener, how about supporting different MaxCircuitDirtiness values for each?

SocksPort 127.0.0.1:9050 SocksPort 127.0.0.1:9060 Max(Circuit)Dirtiness 480 SocksPort 127.0.0.1:9070 IsolateDestAddr Max(Circuit)Dirtiness 1200

I don't want to deprecate MaxCircuitDirtiness as it is right now. The option could be named MTTA (MaxTimeToAttach) or similar. Unset uses the default value of MaxCircuitDirtiness. Maybe the value -1 disables it for that listener.

Setting a lowest possible value should be considered to avoid clients overloading the network.

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