Opened 9 years ago

Closed 8 years ago

#2114 closed defect (fixed)

Vidalia network map should distinguish circuit types

Reported by: arma Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version:
Severity: Keywords: networkmap
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by arma)

In Vidalia's network map we show circuits that Tor is building. That's great, but there are cases where it confuses users. In particular, some Tor circuits are 1-hop (for fetching directory information but also using a layer of encryption), and some are internal (for everything other than attaching exit streams). Many users are concerned by the one-hop circuits they see (thinking that Tor is planning to use them for exit streams), and a smaller but still significant number of users set ExcludeExitNodes and then freak out when Tor uses that node as the last hop in an internal (non-exit) circuit. I think both cases would be partially resolved by having Vidalia present the circuit list more clearly.

How would we do this? One option would be a "type" column in the circuit listing, where we describe each circuit as "directory", "exit", or "internal". Another option would be to have separate rows in the circuit listing: put all the exit circuits at the top under the heading "exit circuits", then "internal circuits" and the list of internal circuits, then finally all the 1-hop directory circuits with their own heading. I like option 2 slightly better. I wonder if there are still better approaches?

Vidalia can learn the circuit purpose via the controlport, from the (alas undocumented) "PURPOSE=" argument in circuit status. But I think we don't export other flags, like "build_state->onehop_tunnel". We should first change Tor so it exports these flags in a more usable way.

Child Tickets

TicketStatusOwnerSummaryComponent
#2411closedrransomexpand getinfo circuit-status to show build_state flagsCore Tor/Tor

Change History (7)

comment:1 Changed 9 years ago by arma

I think an earlier step here is that Tor needs to export the circuit bits in a more reliable way. There's no purpose= arg in the Tor spec, but the code looks like we added something. But I think it added 'general' or 'controller', which doesn't include 'internal or not' or 'onehop or not'. Somebody should probably open a new trac entry for that topic, and make this one its parent.

comment:2 Changed 9 years ago by arma

Description: modified (diff)
Summary: The network map should distinguish between general and internal circuitsVidalia network map should distinguish circuit types

comment:3 Changed 9 years ago by arma

I made #2411 for the Tor side of the bug.

comment:4 Changed 8 years ago by nickm

Type: defectproject

comment:5 Changed 8 years ago by chiiph

Keywords: networkmap added

comment:6 Changed 8 years ago by rransom

Type: projectdefect

Changing this ticket back to ‘defect’ now that our Trac allows defects to have child tickets.

comment:7 Changed 8 years ago by chiiph

Resolution: fixed
Status: newclosed

A fix for this is in my branch chiiph/bug2114_circuits. It has been merged to alpha and it will be out with 0.3.2.

Note: See TracTickets for help on using tickets.