[tor-bugs] #2113 [Tor Client]: getinfo/event to learn what circid you would use if you get a stream for ip:port

[Tor Bug Tracker & Wiki]

#2113: getinfo/event to learn what circid you would use if you get a stream for
ip:port
-------------------------+--------------------------------------------------
 Reporter:  arma         |       Owner:                  
     Type:  enhancement  |      Status:  new             
 Priority:  normal       |   Milestone:  Tor: unspecified
Component:  Tor Client   |     Version:                  
 Keywords:               |      Parent:                  
-------------------------+--------------------------------------------------
Changes (by nickm):

  * milestone:  => Tor: unspecified


Comment:

 I sorta question how useful this is: certainly there are issues.  These
 issues include:
    * There is an inherent race condition here if circuits change between
 the GETINFO and the connection.
    * Having a function like this would also get confusing if we ever have
 more than 2 circuits that we could use for a given address.
    * Also, some of the proposal 171 stuff would conflict with this, as
 there would be more inputs than just addr:port that would determine which
 circuit got used.
    * Most of the interfaces I could think of for actually *using* this
 feature would confuse users by promising "your IP will seem to be (the
 exit node I got when I asked about www.example.com:80)" when in fact they
 could well get a different IP when they go to www.strange-
 port.example.com:9090, or some address with a trackexithost, or whatever.

 So I think if we do this, we should start with somebody figuring out a
 sane UI so we can work backwards from that.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2113#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online