Opened 4 years ago

Last modified 2 years ago

#18082 new enhancement

Log separate HS extra-info stats for Single Onion Services

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs, statistics, privcount-maybe, single-onion
Cc: mikeperry Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor: SponsorQ-can

Description

To determine guard and middle weights accurately, we need to log separate extra-info statistics for RSOS and SOS.

Since they have the same path length, I think they can be combined into a single category.

See:
https://lists.torproject.org/pipermail/tor-dev/2016-January/010218.html

Child Tickets

Change History (16)

comment:1 Changed 4 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final

It is impossible that we will fix all 226 currently open 028 tickets before 028 releases. Time to move some out. This is my second pass through the "new" and tickets, looking for things to move to 0.2.9.

comment:2 Changed 4 years ago by teor

Cc: mikeperry added
Parent ID: #17178

Unfortunately, it is not possible to separate the statistics for Rendezvous Single Onion Services (RSOS), as the hidden service statistics are measured at the HSDir and Rendezvous Point relays, and not at the hidden service itself. These relays have no way of knowing whether they are connected to a RSOS or not.

The impact of this is:

  • Rendezvous Single Onion Services will appear as Hidden Services in the HSDir and Rendezvous Point statistics
  • Single Onion Services will appear as Hidden Services in the HSDir statistics only (they don't do Rendezvous)

However, it is possible to keep separate statistics on cells seen by a relay via Single Onion Service extend requests.
HSDirs can log requests for Single Onion Service descriptors separately, as they are the only descriptors that contain an extend-info line. However, it's may not be worth implementing, as the encryption in proposal 224 will stop HSDirs reading HS descriptors.

We could have Rendezvous Single Onion Services add an identifying line to their descriptors, but we'd have to do it in a way that allowed clients to still parse the descriptors. That would only get us the HSDir statistics anyway.

That said, if we identify RSOS in their descriptor so Tor2web clients don't connect to them (#17945), we could use the identifier for statistics as well.

I'll look at this again in 0.2.9.

comment:3 Changed 4 years ago by asn

Keywords: tor-hs added
Points: medium

comment:4 Changed 3 years ago by isabela

Points: medium3

comment:5 Changed 3 years ago by isabela

Keywords: isaremoved added
Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

comment:6 Changed 3 years ago by teor

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

Milestone renamed

comment:7 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:8 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:9 Changed 2 years ago by nickm

Keywords: isaremoved removed

comment:10 Changed 2 years ago by nickm

Keywords: statistics privcount-maybe added

comment:11 Changed 2 years ago by teor

Summary: Log separate HS extra-info stats for RSOS (and SOS)Log separate HS extra-info stats for Single Onion Services

PrivCount only runs on relays.
A relay could guess it was connected to a single onion service by working out it was an intro or rend point directly connected to a client.

comment:12 Changed 2 years ago by teor

If we were going to do this, we should measure the client side as well, so we can track Tor2web usage.

comment:13 Changed 2 years ago by teor

I'm tracking this in these PrivCount tickets:
Intro Service: https://github.com/privcount/privcount/issues/342
Intro Client: https://github.com/privcount/privcount/issues/343
Rend: https://github.com/privcount/privcount/issues/344

Note that any Tor2web stats on relays would be biased by Tor2webRendezvousPoints.

comment:14 Changed 2 years ago by teor

Keywords: single-onion added; rsos removed

Now there's only one kind of single onion service, change rsos to single-onion

comment:15 Changed 2 years ago by teor

Keywords: sos removed

Now there's only one kind of single onion service, remove all references to old sos tag

comment:16 Changed 2 years ago by nickm

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