Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 313
    • Issues 313
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #32859
Closed
Open
Created Dec 30, 2019 by Trac@tracbot

Tor man docs missing DoS log example

In "DENIAL OF SERVICE MITIGATION OPTIONS" man section, there is:

"If any of the DoS mitigations are enabled, a heartbeat message will appear in your log at NOTICE level which looks like:

DoS mitigation since startup: 429042 circuits rejected, 17 marked addresses. 2238 connections closed. 8052 single hop clients refused. The following options are useful only for a public relay. They control the Denial of Service mitigation subsystem described above."

However, Tor daemon actually logs:

"DoS mitigation since startup: x circuits killed with too many cells. y circuits rejected, z marked addresses. m connections closed. n single hop clients refused."

I propose:

  1. adding log examples for each of the 3 log mitigation options, in their sections.

  This perhaps will make more clear what "too many cells" means, as there seem to be no other documentation sources regarding this.

  1. adding the **"x circuits killed with too many cells" **in the final log example.

Trac:
Username: JoeBeeez

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking