[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #3290 [Tor]: Circuit reuse for FTP (and other?) multi-connection protocols



#3290: Circuit reuse for FTP (and other?) multi-connection protocols
-----------------------------+------------------------------
     Reporter:  supercyborg  |      Owner:
         Type:  enhancement  |     Status:  reopened
     Priority:  normal       |  Milestone:  Tor: unspecified
    Component:  Tor          |    Version:
   Resolution:               |   Keywords:  FTP tor-client
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+------------------------------
Changes (by nickm):

 * status:  closed => reopened
 * resolution:  duplicate =>
 * milestone:   => Tor: unspecified


Comment:

 I think this is the kind of thing that would best be done with explicit
 configuration or application-level hinting as suggested in proposal 229.
 Or maybe we could tweak the behavior of one of the really fine-grained
 circuit isolation modes so that eg use of the same socks username/password
 could count as instructions to

 But I don't think we would want to have a general rule saying "always use
 the same circuit for a given IP if you already have a connection that's
 using that IP."  It seems there's probably some way to exploit that to
 track clients across websites when you otherwise wouldn't be able to.

 In any case, there's no reason not to look for a better way to do this.
 So, reopening and assigning the unspecified milestone.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3290#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs