[tor-bugs] #8405 [Tor]: Provide a control port command to query the circuit used for SOCKS u+p
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Jul 17 21:25:22 UTC 2014
#8405: Provide a control port command to query the circuit used for SOCKS u+p
-----------------------------+------------------------------------
Reporter: mikeperry | Owner: mikeperry
Type: enhancement | Status: needs_revision
Priority: normal | Milestone: Tor: 0.2.6.x-final
Component: Tor | Version:
Resolution: | Keywords: tor-client, mike-0.2.5
Actual Points: | Parent ID: #5752
Points: |
-----------------------------+------------------------------------
Comment (by arthuredelstein):
Replying to [comment:13 nickm]:
> > Does this seem like the right thing now?
>
> Before I review this one, I'd like to hear from the TBB team about
whether this general approach meets their needs. I don't think I've seen
an answer there. ''I'm'' happy with an events-based approach, but the
whole point of this ticket is to improve TBB usability, so I'd like to
know whether we're actually going to do that before we merge.
To summarize: I'm working on #5752 (isolate streams by URL bar domain) and
descendants. I have implemented a patch for #3455, where the browser is
using a unique SOCKS username and password (u+p) for each URL bar domain,
and tor accordingly sets up a separate circuit for each unique u+p. The
next step (#8641) is to implement a UI, attached to the browser's URL bar,
that shows the progress of a circuit as it's being built, and the exit IP
of that circuit. So we need to be able to query/monitor tor for the
circuit ID corresponding to the u+p.
At this point, I don't expect to need any isolation flags apart from SOCKS
u+p. So we could remove the other isolation flag stuff from the patch.
But, given the work Robert was doing, I imagined you might want all
isolation flags covered, for the sake of completeness. I'd be glad to hear
your opinion either way.
In the meantime I can start working with the TBB team on a design and
prototype for the #8641 UI, which may help solidify exactly what we need
in the patch for this ticket. Any suggestions are much appreciated!
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8405#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list