Re: [T(A)ILS-dev] Bug#623203: Bug#623203: vidalia: config sc…

Delete this message

Reply to this message
Autor: intrigeri
Data:  
A: Dererk
CC: 623203, The Tails public development discussion list
Assumpte: Re: [T(A)ILS-dev] Bug#623203: Bug#623203: vidalia: config script kills system-wide Tor daemon while instructed to let it alone
Dererk wrote (18 Apr 2011 17:17:46 GMT) :
> I understand now where the issue resides... You are apparently using
> an old version of Vidalia.


As my initial bug report meta-data displays, this is Debian Squeeze's
Vidalia 0.2.10-3.

> You may see it from here[1] that at least 8-month-old version is not
> using that .config file anylonger.


You uploaded to sid the Vidalia version I have reported this bug
against on 2010-10-19. As far as the Git repository mentioned in the
Vcs-Git control field can tell me, this config file has not been
changed since then: last change to this file was made at commit
7db077b9 on 2010-09-27.

I additionally checked the .config file shipped in the actual packages
currently in the Debian archive (both stable's 0.2.10-3 and unstable's
0.2.12-1) both are the same as the one in Git. So it appears to me I
am *not* talking of an outdated file when reporting this bug and
proposing a patch that might fix it. In case you need to triple-check,
this file's sha1sum is 67cb93d9be9533a2c7045b49e48821e7caa9eb5e. Has
the $RANDOM cabal sent me four times the same outdated buggy file when
I downloaded it using four different ways?

The Git patch I proposed may very well be wrong, and I'd be happy to
stand corrected, but I dare pretending once more I prepared it
"against current packaging repository master branch".

Am I plain wrong from the beginning to the end?

Side note: to reproduce this bug, you'll need to:

  1. run a Debian Squeeze system (I'm pretty sure testing/unstable
     would do, too) that has a system-wide Tor daemon running.
  2. setup a Debian Squeeze chroot inside it
  3. enter the chroot. all following steps happen in there.
  4. preseed vidalia's vidalia/tor-daemon-interaction to "nothing"
  5. apt-get install vidalia tor
  => vidalia.config kills the Tor daemon that was running outside the
     chroot; IMHO this is not the documented behaviour.


In my book,

  if [ "$RET" = "nothing" ] || [ "$RET" = "one-off" ]; then
    echo -n "Stopping tor daemon: "
    pkill -x tor > /dev/null && echo "tor." || echo 'Failed!'


means:

  if [ I shall *not* interfere with the system-wide Tor daemon ] or [ whatever ]; then
    kill Tor
  fi


Feels wrong, doesn't it?

Bye,
--
intrigeri <intrigeri@???>
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
| We're dreaming of something else.
| Something more clandestine, something happier.