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

Closed (moved)
Open
Opened Sep 11, 2012 by Mike Perry@mikeperry

Restore consensus-governed path bias messages

The log line for the check against pathbias_get_notice_rate() in entry_guard_inc_first_hop_count() should not have been demoted to info level. We have a consensus parameter to govern it if it really gets out of hand. It can be fully disabled using this parameter, just like the warn message can be and is. The warn should not have been demoted either.

I'm setting this as 'major' based on #6537 (moved)'s priority. I don't believe it is rational to merge #6537 (moved) and #6538 (moved) into 0.2.2.x and 0.2.3.x without also informing the user about the possibility a significantly more serious active attack.

I can fix the log message to be less threatening as part of this. I would also like to do this commit on top of the #6647 (moved) backport.

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