On Tue, 19 Apr 2011, intrigeri wrote:
> > In relation to this matter, there's an extremely interesting point
> > that I've found to accomplish this, and it's very very simple to
> > achieve: A better solution on Debian would be to use Tor's
> > ControlSocket, which allows Vidalia to talk to Tor via a Unix domain
> > socket, and could possibly be enabled by default in Tor's Debian
> > packages. Vidalia can then authenticate to Tor using
> > filesystem-based (cookie) authentication if the user running Vidalia
> > is also in the debian-tor group.
That was the reason why I patched Tor to support unix domain sockets in
the first place. It has taken a while to get there, and I'm afraid we
still aren't quite at the goal yet.
> 1. In the default torrc: set ControlSocket to /var/run/tor/control.socket
You will need to make sure Tor creates the socket with correct
permissions, I think. Once it does that, enabling it in the Debian
package seens doable.
Editing /etc/tor/torrc is a no-go. That just becomes a horrible mess.
Ideally tor would start to support an /etc/tor/torrc.d/ style directory,
but for now I guess we can add it to the default debian config we patch
into the tor binary.
So:
- ensure the socket is created with sane permissions that allow things
to work (or tell me that isn't necessary),
- then we enable it by default.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `- http://www.debian.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
