Opened 5 years ago

Last modified 2 years ago

#13466 new enhancement

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

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay, tor-hs, privcount-maybe needs-design metrics
Cc: Actual Points:
Parent ID: #13195 Points:
Reviewer: Sponsor: SponsorQ-can

Description

In #13195 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.

Child Tickets

Change History (9)

comment:1 Changed 4 years ago by nickm

Keywords: SponsorR removed
Sponsor: SponsorR

Bulk-replace SponsorR keyword with SponsorR sponsor field in Tor component.

comment:2 Changed 4 years ago by dgoulet

Sponsor: SponsorRSponsorR-can

Move those from SponsorR to SponsorR-can.

comment:3 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:4 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:5 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:6 Changed 2 years ago by dgoulet

Keywords: tor-hs added
Severity: Normal
Sponsor: SponsorR-can

comment:7 Changed 2 years ago by nickm

Keywords: privcount-maybe needs-design metrics added

comment:9 Changed 2 years ago by nickm

Sponsor: SponsorQ-can
Note: See TracTickets for help on using tickets.