Your message dated Thu, 03 Nov 2011 10:35:21 +0000
with message-id <[email protected]>
and subject line Bug#642220: fixed in torsocks 1.2-1
has caused the Debian Bug report #642220,
regarding torsocks: Can't connect to hidden services anymore.
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.)
--
642220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642220
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: torsocks
Version: 1.1+git20110826-1
Severity: important
After upgrading to version 1.1+git20110826-1, any attempts to use torsocks
to connect to a hidden service fails with error:
# torsocks ssh xxxxx.onion
15:11:16 libtorsocks(8037): SOCKS V4 connect rejected:
15:11:16 libtorsocks(8037): SOCKS server refused connection
As a matter of fact, /var/log/tor/log has some explanations:
Sep 20 15:11:16.156 [warn] Your application (using socks4 to port 22) is giving
Tor only an IP address. Applications that do DNS resolves themselves may leak
information. Consider using Socks4A (e.g. via privoxy or socat) instead. For
more information, please see
https://wiki.torproject.org/TheOnionRouter/TorFAQ#SOCKSAndDNS.
Sep 20 15:11:16.156 [warn] Rejecting SOCKS request for anonymous connection to
private address [scrubbed]
It seems that there have been a lot of code refactoring done by upstream
lately that has broken the hidden service part of torsocks, in particular
the resolving part for onion names.
Using the debug mode give some more informations:
# TORSOCKS_DEBUG=3 torsocks ssh xxx.onion
[SNIP]
15:19:49 libtorsocks(8250): address: 127.0.0.0 is local
15:19:49 libtorsocks(8250): Beginning handle loop for socket 3
15:19:49 libtorsocks(8250): In request handle loop for socket 3, current state
of request is 0
15:19:49 libtorsocks(8250): Connecting to 127.0.0.1 port 9050
15:19:49 libtorsocks(8250): Connect returned 0, errno is 107
15:19:49 libtorsocks(8250): Socket 3 connected to SOCKS server
15:19:49 libtorsocks(8250): In request handle loop for socket 3, current state
of request is 2
15:19:49 libtorsocks(8250): In request handle loop for socket 3, current state
of request is 3
15:19:49 libtorsocks(8250): Writing to server (sending 17 bytes)
15:19:49 libtorsocks(8250): Sent 17 bytes of 17 bytes in buffer, return code is 0
15:19:49 libtorsocks(8250): In request handle loop for socket 3, current state
of request is 5
15:19:49 libtorsocks(8250): Receiving reply to SOCKS V4 connect request
15:19:49 libtorsocks(8250): In request handle loop for socket 3, current state
of request is 4
15:19:49 libtorsocks(8250): Reading from server (expecting 8 bytes)
15:19:49 libtorsocks(8250): Received 8 bytes of 8 bytes expected, return code
is 0
15:19:49 libtorsocks(8250): In request handle loop for socket 3, current state
of request is 6
15:19:49 libtorsocks(8250): SOCKS V4 connect rejected:
15:19:49 libtorsocks(8250): SOCKS server refused connection
while with the previous version of torsocks, everything went fine:
[SNIP]
15:23:17 libtorsocks(8976): address: 127.0.0.0 is local
15:23:17 libtorsocks(8976): Beginning handle loop for socket 3
15:23:17 libtorsocks(8976): In request handle loop for socket 3, current state
of request is 0
15:23:17 libtorsocks(8976): Connecting to 127.0.0.1 port 9050
15:23:17 libtorsocks(8976): Connect returned 0, errno is 107
15:23:17 libtorsocks(8976): Socket 3 connected to SOCKS server
15:23:17 libtorsocks(8976): In request handle loop for socket 3, current state
of request is 2
15:23:17 libtorsocks(8976): get_pool_entry: searching for: 127.0.69.0
15:23:17 libtorsocks(8976): get_pool_entry: found: xxx.onion
15:23:17 libtorsocks(8976): In request handle loop for socket 3, current state
of request is 3
15:23:17 libtorsocks(8976): Writing to server (sending 40 bytes)
15:23:17 libtorsocks(8976): Sent 40 bytes of 40 bytes in buffer, return code is 0
15:23:17 libtorsocks(8976): In request handle loop for socket 3, current state
of request is 5
15:23:17 libtorsocks(8976): Receiving reply to SOCKS V4 connect request
15:23:17 libtorsocks(8976): In request handle loop for socket 3, current state
of request is 4
15:23:17 libtorsocks(8976): Reading from server (expecting 8 bytes)
15:23:46 libtorsocks(8976): Received 8 bytes of 8 bytes expected, return code
is 0
15:23:46 libtorsocks(8976): In request handle loop for socket 3, current state
of request is 6
15:23:46 libtorsocks(8976): Handle loop completed for socket 3 in state 13,
returning 0
Seems that in the new version the get_pool_entry part is bypassed.
I'm using the DNSPort and AutomapHostsOnResolve options in /etc/tor/torrc.
Setting tordns_enable to false in /etc/torsocks.conf doesn't resolve the
problem (as expected).
-- System Information:
Debian Release: wheezy/sid
Versions of packages torsocks depends on:
ii libc6 2.13-18
Versions of packages torsocks recommends:
ii tor 0.2.2.32-1
torsocks suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: torsocks
Source-Version: 1.2-1
We believe that the bug you reported is fixed in the latest version of
torsocks, which is due to be installed in the Debian FTP archive:
torsocks_1.2-1.debian.tar.gz
to main/t/torsocks/torsocks_1.2-1.debian.tar.gz
torsocks_1.2-1.dsc
to main/t/torsocks/torsocks_1.2-1.dsc
torsocks_1.2-1_amd64.deb
to main/t/torsocks/torsocks_1.2-1_amd64.deb
torsocks_1.2.orig.tar.gz
to main/t/torsocks/torsocks_1.2.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.
Patrick Matthäi <[email protected]> (supplier of updated torsocks 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: SHA256
Format: 1.8
Date: Thu, 03 Nov 2011 11:12:56 +0100
Source: torsocks
Binary: torsocks
Architecture: source amd64
Version: 1.2-1
Distribution: unstable
Urgency: low
Maintainer: Patrick Matthäi <[email protected]>
Changed-By: Patrick Matthäi <[email protected]>
Description:
torsocks - use socks-friendly applications with Tor
Closes: 636943 642220 647097
Changes:
torsocks (1.2-1) unstable; urgency=low
.
* New upstream release.
Closes: #647097
- Unresolved symbol warnings should be realy gone now.
Closes: #636943
- Connect to hidden service should work now.
Closes: #642220
- Remove wrong installed files from usr/share/.
Checksums-Sha1:
5e877f0b04983b64c296e0d31e81f14c54619b0d 1730 torsocks_1.2-1.dsc
b8afeb217db299892a628e28f2327a1d2697f9ad 456453 torsocks_1.2.orig.tar.gz
8f6c93e95bfa4d15ae9ea93aa4558390f2ff9c31 3190 torsocks_1.2-1.debian.tar.gz
ad6154ffe88d4015321d5aaacb385ec09467d27e 76136 torsocks_1.2-1_amd64.deb
Checksums-Sha256:
a49fab219dfe5347cc3aaccb41bfd56495f2a3918d8eee225f6766f1cc814ca0 1730
torsocks_1.2-1.dsc
bea57d3624d723724fd1e260f0e6b2a354c0da742c023aa994c7692270d111d4 456453
torsocks_1.2.orig.tar.gz
20671b49ec40d634c29e1883efba72bf96f149c1326a4e37376666a92c882c7d 3190
torsocks_1.2-1.debian.tar.gz
5d96d6d391621fd945f877af1eebed514072db0c95e88125622748bceaf88e03 76136
torsocks_1.2-1_amd64.deb
Files:
ab71aa7a2e217293259ae715b573ff31 1730 net optional torsocks_1.2-1.dsc
9bdc8786951e7eec6915433f324f22a4 456453 net optional torsocks_1.2.orig.tar.gz
c0c7fdc10513e0ddc4fb1a927b2a19ea 3190 net optional torsocks_1.2-1.debian.tar.gz
98024b978a1c73158fb2b7a4df8bdba9 76136 net optional torsocks_1.2-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQIcBAEBCAAGBQJOsmwrAAoJEBLZsEqQy9jkW3kP/0SsGqJNKSxB2gub418MVfD5
+6ZpJQvHe2NVWw2+9kgv1Yx6Lx8oq2ELGgmZgCeCabVP8VIA0L9QvpLn02s/zRuQ
feXn3hh4U89/uhuS8WWS+6DjMKQO9oKVaiyagqNGWB2GQRd0hvWVBODc+3WVLJ4X
r27HXWNJvHVlzIvLuV+/styqlw04E2+OeGMWpeRY82A9AmxSiTyaxHcVPf0t9V4T
lbuD3r3akVBk4t+PrtYiFXqgMDGrzzt4qjh9VIR5mHoU8Wr95MojnyxSddB2CArq
wAphMQmp6N8vqZNkl9l6vFM6Hcp9zMDr+yrov4fd48q61U8lj80Gt0Ppkeh4I837
xVpz+20v6CcspLLpbbT/oPvggiRfk1OM+GRmanVyTzSGWK5rtlIEsY1TjpOdDuo6
NFAESXGvKL+z+6rR8+XGYvJE4p3u5Ye60cdy1aQUg7obdH7gDPnDLKmsSFCyIZWp
TVwJnhhSKOgebKDEg4AH5ZuO1XAvIFPpJj6QAwAdVjjkRyd1DU4vqWZ4igYsEcCB
Hl0ySqHzPVO4xACtPnrjMqZ2EJlrV/UAABxrH+Ek58yjDW7SyHhWfqORiJKJTuHl
VIjAJINCcAii4oqaBC+ZODo/XpyFGtd5Ky4jLmAeCzoyRtp37dX6f9/1NHNpW3Wu
3HLekHWMwF6TSEmX9NF6
=r100
-----END PGP SIGNATURE-----
--- End Message ---
