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

Re: [tor-bugs] #16824 [Tor]: coexistence of client and relay processing on same thread poses traffic confirmation risk

#16824: coexistence of client and relay processing on same thread poses traffic
confirmation risk
---------------------------+--------------------------------
     Reporter:  starlight  |      Owner:
         Type:  defect     |     Status:  new
     Priority:  normal     |  Milestone:  Tor: 0.2.7.x-final
    Component:  Tor        |    Version:  Tor: 0.2.6.10
   Resolution:             |   Keywords:  PostFreeze027
Actual Points:             |  Parent ID:
       Points:             |
---------------------------+--------------------------------

Comment (by starlight):

 Replying to [comment:6 mikeperry]:
 > circuit formation and client usage is even more visible when there is
 not relay traffic involved

 Agreed, no doubt w/r/t pure-client operation.

 I have two thoughts:

 1) in general, if two configurations or implementations
 exist, x1 and x2 where x2 is more anonymous than x1,
 one should prefer x2

 2) some consider it a reasonable idea to configure a client
 and relay in the same daemon instance with the belief
 that this would obfuscate local client traffic to some
 degree; but with the implementation as it presently
 stands such an idea is false and should be denigrated

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16824#comment:7>
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