Opened 20 months ago

Last modified 15 months ago

#24047 new defect

Add new stats for v2 and v3 onion service traffic

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop224, tor-hs, privcount-maybe, 034-triage-20180328, 034-removed-20180328
Cc: Actual Points:
Parent ID: Points: 2
Reviewer: Sponsor:

Description

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 before we implement this.

Child Tickets

Change History (4)

comment:1 Changed 17 months ago by dgoulet

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

Moving a bunch of tickets from 033 to 034.

comment:2 Changed 15 months ago by nickm

Keywords: 034-triage-20180328 added

comment:3 Changed 15 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:4 Changed 15 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

Note: See TracTickets for help on using tickets.