[tor-bugs] #6342 [Tor Client]: different streams have too close exit node IP's

[Tor Bug Tracker & Wiki]

#6342: different streams have too close exit node IP's
------------------------+---------------------------------------------------
 Reporter:  proper      |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  major       |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor Client  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
Changes (by proper):

  * milestone:  => Tor: 0.2.4.x-final


Comment:

 The bug is reproducible. I tested it again.

 This is not about TransPort vs SocksPort. It's also about SocksPort stream
 isolation from other SocksPorts.

 For testing I created 6 different SocksPorts. 127.0.0.1 9061, 9062, 9063,
 9064, etc... And then I pointed the browser to them, testing them one by
 one.

 SocksPort 9061 got IP $x.$y.$z.1.
 SocksPort 9065 got IP $x.$y.$z.2.

 Those nodes have the same ISP, they are probable owned by the same people
 and they are probable in the same Tor server family.

 All other SocksPorts got different exit IPs, i.e. $a.$b$.$c.$d.

 That doesn't mean it takes 5 different SocksPorts to produce this. Could
 be also happen already for two.

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