Opened 6 years ago

Closed 5 years ago

#9669 closed task (duplicate)

Add extrainfo lines for Hidden Service usage stats?

Reported by: asn Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Keywords: tor tor-hs needs-proposal
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I wonder if it would be a good idea to have usage statistics of the Hidden Services network.

This could happen in two ways:
a) Tor relays could send a line in their extrainfo descriptor saying how many bytes of rendezvous connections they have pushed. This would give us an idea of the bandwidth usage of Hidden Services.
b) HSDirs and Introduction Points could send statistics about how many HS descriptors they have sent, or how many intro requests they have performed.

I think a) is easy to implement and *probably* privacy-preserving too (since RPs are picked randomly by the client out of the set of all Tor relays). Would also give us an idea on how much HSes are used. However, we should think scenarios where revealing usage stats of an RP might compromise the anonymity of the HS or its clients.

The b) idea is probably too leaky to be worth it. Since IPs and HSDirs correspond to specific Hidden Services and leaking info about them might hurt the privacy of the HS.

I'm still not sure if this is worth it, but it would be good to consider.

Child Tickets

Change History (2)

comment:1 Changed 6 years ago by nickm

Keywords: needs-proposal added
Milestone: Tor: unspecified

comment:2 Changed 5 years ago by dgoulet

Resolution: duplicate
Status: newclosed

Closing it because we now have proposal 238 (https://gitweb.torproject.org/torspec.git/tree/proposals/238-hs-relay-stats.txt) for this and #13192 has been merged in 0.2.6 to report two statistics.

See https://metrics.torproject.org/hidserv-data.html.

Other statistics that are being considered can be found: #13195, #13466, and more are being evaluated at the moment so ticket will be opened has they are being implemented.

Marking it as "duplicate" which is the closer to the thruth than "implemented"

Note: See TracTickets for help on using tickets.