[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #6609 [Tor Client]: Proposal to add tor-connect utility to tor-core distribution
#6609: Proposal to add tor-connect utility to tor-core distribution
-------------------------+--------------------------------------------------
Reporter: tri | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Tor Client | Version:
Keywords: | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by rransom):
Replying to [comment:2 tri]:
> * On every operating system on which using an external command as a
> proxy is likely to work (i.e. Linux and MacOS), the copy of Tor
> packaged in TBB is configured to choose a random SOCKS server port
> every time it runs. There is no good way to communicate Tor's current
> SocksPort to any program run separately from the bundle.
>
> I know. That's why I'd put the command into the bundle and pass the
> port information using the same'ish mechanism used when passing
> the information to the browser. The port number anyways appears
> semi-magically in the browser configuration.
Tor communicates its SocksPort to Vidalia using the Tor control-port
protocol (how ''that'' gets set up is rather ugly). Vidalia then provides
the SOCKS proxy port to TBB-Firefox by setting an environment variable.
This technique cannot work for any process that is not started by Vidalia.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6609#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