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
  • Activity
  • Create a new issue
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #9188

Closed (moved)
Open
Opened Jul 01, 2013 by Nick Mathewson@nickm🐭

Our weighting algorithms probably behave strangely when guards are disabled

Most of our design for weighting and path-selection algorithms includes an assumption that guard nodes are going to get used (since urning off guards in normal use is a really bad idea). But some scanning and measurement tools want to run with guards disabled, and have Tor construct random paths. We should make sure that the random paths Tor generates in that case are sensible.

For example, we currently require the first hop to have the Guard flag, even if UseGuards is off. Is that good? Should we change it? What else do we need here?

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: legacy/trac#9188