[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2091 [Vidalia]: Support ControlSocket as well as ControlPort
#2091: Support ControlSocket as well as ControlPort
-------------------------+--------------------------------------------------
Reporter: arma | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Vidalia | Version:
Keywords: | Parent:
-------------------------+--------------------------------------------------
Comment(by chiiph):
From a quick look it seems this can be easy to implement in Vidalia.
What I still don't get is what's the difference between setting Tor's
ControlPort or setting ControlSocket path, because if Tor's already
running, you have to either set one control or the other to communicate,
and if Tor isn't running, Vidalia won't be able to call the init script,
since it's a service and as such it must be initiated as root.
For what I understand ControlSocket only provides a different way of
communicating to Tor, it doesn't give any extra control over it. But may
be I'm getting this wrong.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2091#comment:1>
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