On Mon, 24 Mar 2008, Jacob Appelbaum wrote: > Peter Palfrader wrote: > > On Fri, 21 Mar 2008, Adna rim wrote: > > > >> My solution at the moment is stopping the tor daemon and removing it > >> from the runlevels through vidalia's postinst script. > > > > Mucking with another package's config is a serious policy violation. > > Such a package would never be acceptable for Debian. > > > > > > That was my thought as well. However, I'm curious what your thoughts are > on the Debian Way (TM) to solve this problem? Perhaps to patch the tor > init.d script in the Tor package to check for a flag that can be set by > the Vadalia package?
I have explained it more than once. I think the proper way is to teach vidalia to use a control unix domain socket and have it use the Tor that is installed and running on the system. Once vidalia knows how to do that I can enable the control socket in the package by default. Peter
