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

Closed (moved)
Open
Created Oct 30, 2017 by teor@teor

Add new stats for v2 and v3 onion service traffic

The current onion service traffic statistic includes v2 and v3 services.

But they are distinguishable at the rend point: v2 services use TAP to extend, and v3 use ntor.

This is how we tag and count circuits for v2 and v3 in experimental PrivCount: https://github.com/privcount/tor/commit/ab0ee674d72a8b86cf394ecb392c0e829a265cf6 (Sorry it's not a very clean commit, look for circ->used_legacy_circuit_handshake.)

We could add a similar flag to tor, and use that flag to produce two new statistics, v2 and v3 data.

Since there will be a small number of v3 onion sites, we might want to implement this using PrivCount in tor, so their rend points do not stand out. If we don't use PrivCount in tor, we should fix the stats noise bugs in #23061 (moved) before we implement this.

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