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

Closed (moved)
Open
Opened Oct 31, 2011 by Roger Dingledine@arma

Minimize time between new relay appearing and having some bw vote for it

In #2286 (moved) I point out a huge security problem in Tor, which is that new relays can lie about their bandwidth and get away with it.

One of the components of my suggested fix is to minimize the period of time between when a new relay appears in the network, and when we have an opinion about its bandwidth.

So it would be great for the bwauths to recognize new relays and schedule them for high-priority tests.

Or is that already done? What's the expected turnaround time?

This ticket is perhaps related to #2550 (moved).

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