Re: [tor-bugs] #1967 [Tor Client]: The ancient architecture of Tor!!

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#1967: The ancient architecture of Tor!!
--------------------+-------------------------------------------------------
 Reporter:  bee     |         Type:  enhancement
   Status:  closed  |     Priority:  normal     
Milestone:          |    Component:  Tor Client 
  Version:          |   Resolution:  not a bug  
 Keywords:          |       Parent:             
--------------------+-------------------------------------------------------
Changes (by ioerror):

  * status:  new => closed
  * resolution:  => not a bug


Comment:

 We've long discussed possibly creating a shared library. You're not the
 first and you won't be the last to suggest it - You're simply the most
 annoying, we all wish you'd knock it off but that's probably a lost cause.

 However, it's worth answering you because while you will probably never
 cease to be annoying, someone else may discover this bug report and it
 will hopefully help them.

 It's not clear what you'd gain and it's quite clear that it has major
 downsides. There are a lot of problems (network load being a great
 example) that would result from running different instances of Tor in
 every application.

 Consider using 'torsocks' for applications where you want to use Tor as a
 library; it will handle all of the rough edges for you and it uses SOCKS
 to talk to Tor. You can have multiple configurations, one per application
 or other weird configs. As a bonus, it's a linkable library. This is how
 we handle ttdnsd and Tor (though that's with tsocks) interactions.

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