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
  • #13466
Closed
Open
Created Oct 18, 2014 by Roger Dingledine@armaReporter

Collect aggregate stats of ntor-using hidden service interactions vs tap-using interactions

In legacy/trac#13195 (moved) I have a patch to better understand the fraction of Tor traffic that has to do with hidden services, vs the fraction that has to do with exiting.

For the hidden service traffic, we can see if the handshake that extended that hop of the circuit was done using ntor or with tap.

By remembering this bit, we can track fraction of hidden service traffic that came from old Tor 0.2.3.x style bots, vs newer clients. It would be very useful to see this fraction over time.

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