Opened 7 years ago

Closed 7 years ago

#8747 closed enhancement (wontfix)

Add transports field to Onionoo's details documents

Reported by: karsten Owned by:
Priority: Medium Milestone:
Component: Metrics/Onionoo Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Bridges announce their pluggable transports in their extra-info descriptors. We scrub most of that information in the sanitizing process, but at least the transport names survive this process:

@type bridge-extra-info 1.2
extra-info ec2bridgercf30a0b4 7C86C0E30E2E267BB508B7B78A375D740E72B07D
[...]
dirreq-v3-tunneled-dl complete=0,timeout=0,running=0
transport obfs2
bridge-stats-end 2013-04-07 06:43:24 (86400 s)
[...]

Onionoo could add a new field transports to include transport names in its details documents. That would allow bridge operators to at least check whether their bridge announces the configured transports.

Child Tickets

Change History (1)

comment:1 Changed 7 years ago by karsten

Resolution: wontfix
Status: newclosed

On second thought, we already have the "pool_assignment" in details documents which contains pluggable transport information; search for "transport" in https://onionoo.torproject.org/details?type=bridge for examples. If we wanted to add a "transports" field as suggested above, we'd have to parse all bridge extra-info descriptors every hour, which we don't do right now. I'd say that's not worth it. Closing.

Note: See TracTickets for help on using tickets.