Your message dated Sun, 04 Sep 2011 11:18:10 +0000
with message-id <[email protected]>
and subject line Bug#552556: fixed in tor 0.2.3.3-alpha-1
has caused the Debian Bug report #552556,
regarding please enable ControlSocket by default
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
552556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552556
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tor
----- Forwarded message from Dererk <[email protected]> -----
From: Dererk <[email protected]>
Subject: Vidalia-Tor cooperation proposal
To: Peter Palfrader <[email protected]>
CC: Vern Sun <[email protected]>
Date: Tue, 20 Oct 2009 09:53:33 -0300
Message-ID: <[email protected]>
Helo Weasel!
I don't know if you remember me from DC9, unfortunately I didn't
introduced myself properly :-(
Well, let me go straight to the subject:
I wanted to contact you so we could make some plans together in the
Vidalia-Tor integration. I think we have very good stuff to start with,
and that we will end up with a great integration.
First in the list, there's a point you already pointed me to correctly a
few months ago when I asked you for sponsoring, and that is to create a
mechanism in which Vidalia can interact with Tor daemon to tell it not
to start if certain conditions are met.
This conditions are met when users decide to launch Tor's binary from
Vidalia interface, instead that talking though other communication methods.
What I wrongly do now is to ask users to disable Tor's initscripts.
Further more I give some ideas that came into my mind to accomplish a
better approach to this problem.
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.
In the meantime, I thought about a really stupid solution, but that
temporarily solves some of this problems
This is for Vidalia to make a flag, let's say a file-touch (just a flag
file) to /etc/tor/tor.d/ , that Tor's daemon could use to know to avoid
starting, or stuff like that.
Generally speaking, what do you think about this both points? What's
your opinion about this matter?
Hope we can work together about this stuff, and thanks in advance.
Greetings,
Dererk
--
BOFH excuse #359:
YOU HAVE AN I/O ERROR -> Incompetent Operator error.
----- End forwarded message -----
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `- http://www.debian.org/
--- End Message ---
--- Begin Message ---
Source: tor
Source-Version: 0.2.3.3-alpha-1
We believe that the bug you reported is fixed in the latest version of
tor, which is due to be installed in the Debian FTP archive:
tor-dbg_0.2.3.3-alpha-1_amd64.deb
to main/t/tor/tor-dbg_0.2.3.3-alpha-1_amd64.deb
tor-geoipdb_0.2.3.3-alpha-1_all.deb
to main/t/tor/tor-geoipdb_0.2.3.3-alpha-1_all.deb
tor_0.2.3.3-alpha-1.diff.gz
to main/t/tor/tor_0.2.3.3-alpha-1.diff.gz
tor_0.2.3.3-alpha-1.dsc
to main/t/tor/tor_0.2.3.3-alpha-1.dsc
tor_0.2.3.3-alpha-1_amd64.deb
to main/t/tor/tor_0.2.3.3-alpha-1_amd64.deb
tor_0.2.3.3-alpha.orig.tar.gz
to main/t/tor/tor_0.2.3.3-alpha.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Palfrader <[email protected]> (supplier of updated tor package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 3 Sep 2011 22:41:15 UTC
Source: tor
Binary: tor tor-dbg tor-geoipdb
Architecture: source all amd64
Version: 0.2.3.3-alpha-1
Distribution: experimental
Urgency: low
Maintainer: Peter Palfrader <[email protected]>
Changed-By: Peter Palfrader <[email protected]>
Description:
tor - anonymizing overlay network for TCP
tor-dbg - debugging symbols for Tor
tor-geoipdb - geoIP database for Tor
Checksums-Sha1:
c32ca06a7ef80209885c137f4291806beddca864 1587 tor_0.2.3.3-alpha-1.dsc
8cd701aea8442800edfa052f0951c460c854fdeb 2813912 tor_0.2.3.3-alpha.orig.tar.gz
dd415a1c125094194ac8859bac80d25fa1b287dd 31297 tor_0.2.3.3-alpha-1.diff.gz
23a047048b79c1e63a5a8f4b67a5d29b61eb33cc 1233250
tor-geoipdb_0.2.3.3-alpha-1_all.deb
b2bad7b97abd464efc07329411bb26b9b646f9cb 1066398 tor_0.2.3.3-alpha-1_amd64.deb
1734c5b82ce95d33ac93a88182f9fbd45d0e0614 1396354
tor-dbg_0.2.3.3-alpha-1_amd64.deb
Checksums-Sha256:
7dbe1e6a22a7cc2fb831db1603e263846c5077afc23d6d30bf2fc57e3df2b59d 1587
tor_0.2.3.3-alpha-1.dsc
10293bc387769e47dcef308ff1cdeb1fea1b5ad316ff7b82069c43b51da0f129 2813912
tor_0.2.3.3-alpha.orig.tar.gz
25559ea4df560e9fa9dffbb4afb1811f44fe57ce9b0309e2cfa4dad302c786e7 31297
tor_0.2.3.3-alpha-1.diff.gz
1236bb60782f1ff75c425b66bfe4c3302b02354c4a0f938fff613e986bf45c55 1233250
tor-geoipdb_0.2.3.3-alpha-1_all.deb
82947ecb8c1f94a76518896e1f720f721172ea49c95abc6f7db4486272cba54c 1066398
tor_0.2.3.3-alpha-1_amd64.deb
9735571f08f6441aa9097f77b310799372f6853e4c7f895b1ef0fd5061f340b2 1396354
tor-dbg_0.2.3.3-alpha-1_amd64.deb
Closes: 552556
Changes:
tor (0.2.3.3-alpha-1) experimental; urgency=low
.
* New upstream version.
* Upload to experimental now that 0.2.2.x is out of rc and was uploaded to
unstable.
* Merged from debian-0.2.2: 0.2.2.29-beta-1
- The postinst script changes /var/run/tor to mode 02750 if it exists,
but the tor init script creates it with mode 02700 if it doesn't.
Change the init script to also create the directory with a group
writeable mode, the same as the postinst maintainer script, i.e. 02750.
.
This will allow users in the debian-tor group to access the control
socket (re: #552556).
- Enable Control Socket by default. It lives in /var/run/tor/
(closes: #552556).
* Update context in patches/06_add_compile_time_defaults.
* Forward port patches/07_log_to_file_by_default.
Files:
429fd0befa33ff09d83e05ee16537cbf 1587 net optional tor_0.2.3.3-alpha-1.dsc
982feab67723b50cbad31dc73f0e3e16 2813912 net optional
tor_0.2.3.3-alpha.orig.tar.gz
84d6d309b7ed72fa331dd82eddaf4154 31297 net optional tor_0.2.3.3-alpha-1.diff.gz
3c0d086e2a7fbab6594f7deb3006804d 1233250 net extra
tor-geoipdb_0.2.3.3-alpha-1_all.deb
03dca7eeb64fd5a35a1ba636746fdf51 1066398 net optional
tor_0.2.3.3-alpha-1_amd64.deb
ab9e60138f52b7e84d6e44d2e7ca5bd4 1396354 debug extra
tor-dbg_0.2.3.3-alpha-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJOY1wzAAoJEDTSCgbh3sV37rIIALdu7xXHvRbx5Ir1OI7ovPxx
8vWnTUR9GnbKCfa9xJS06aexbqQ3BzMm4C13qq9D0ar09XCxNcDzDmZtJeF9o9S1
BsRtKi2mGe/e6zxMal11m1Q8Ko5LAdZfY9ZYNZXS4/rZECPeRwUBGiGCl7TXvj5H
so0ldNGxMJl4BaMSwb85a0g1cuI2DWT2jjixAaJh7zpHtKPyA24YRnEkizS07a7A
3+zvA3er/4w8PrjyBsbVtd8Uy9W4o4EC3OiX09/l6RmMbC3RDn4mr5TxVOnLAlfc
Pxh5H1TdM8RMuG5zBIpCNYekx6O3/3Vd/1m6PraWUHSCWB1buwTpiDmGz55HWv8=
=1pZs
-----END PGP SIGNATURE-----
--- End Message ---
