Devuan bug report logs - #171
torsocks: can't torify anymore

Package: torsocks; Reported by: Fulano Diego Perez <fulanoperez@cryptolab.net>; Keywords: jessie; dated Fri, 29 Dec 2017 06:33:02 UTC; Maintainer for torsocks is (unknown).


Message received at 171@bugs.devuan.org:


Received: (at 171) by bugs.devuan.org; 12 Apr 2019 12:20:04 +0000
To: 171@bugs.devuan.org
From: Dimitris <dimitris@stinpriza.org>
Subject: Re: works
Date: Fri, 12 Apr 2019 15:10:53 +0300

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--4Evn0R5nxrZ60pjO3BQ8cIuC6bl5sUEBj
Content-Type: multipart/mixed; boundary="fta7B0LzL4HkebKooHYihTZcHJFuUb6dy";
 protected-headers="v1"
From: Dimitris <dimitris@stinpriza.org>
To: 171@bugs.devuan.org
Message-ID: <6f01dfb9-9075-9a53-7edc-7c841e81c848@stinpriza.org>
Subject: Re: works
References: <dedfc35a-3408-00f0-7d36-d9deedee03a5@stinpriza.org>
In-Reply-To: <dedfc35a-3408-00f0-7d36-d9deedee03a5@stinpriza.org>

--fta7B0LzL4HkebKooHYihTZcHJFuUb6dy
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

i'd like to ask, do you use defaults or have you changed things in
torsocks.conf/torrc ? (like listening port?)

--

still using torsocks normally, and retried original scenarios without
any errors. tor running with default settings.
so, can't reproduce this.
anyone else?

d.


--fta7B0LzL4HkebKooHYihTZcHJFuUb6dy--

--4Evn0R5nxrZ60pjO3BQ8cIuC6bl5sUEBj
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQGzBAEBCgAdFiEEddlu1gom7sXWP9ZRvUcY7+WkADkFAlywgE0ACgkQvUcY7+Wk
ADn5+Qv9Fui8kaQQLoJqnZSytPOTSp+93pkiUTIP3R4ksUdbIEV5ed/c7GZI4Zz5
2WiQU8VR17SzVRn7Hv3kNgxyEhwjB9dkzguD6ATLYaASbFZMmJetAORXRkpEOpQG
cw7P5l8HPwq+gFgOBWH2oy8pFbmG9Qz0z4zP5aauHiTZqd2jjixXGkcSqGwwEwe5
GBdjAgjldjM+MUtTdBVk2Exmx1ba/Dz54OcwEsNX4zB+jLne2SY9v1sIAAhdVm8r
RYy1sKMAqSxT1Y0OCd+uVKqNGzuQDXzyI1j9u9pt9bPkJydGY05h9vrO3K/drPSD
Wt9sASLqrc4LFloE901GOecmZklNQ3qS/aA/wwRvDiScVDXWh1lRmRMg6xpCLB9N
97En4Z1ztbJvvMlAn+wKE6zDW54NbAHX0a8VE/0zVPEis5CON0bXWyfW/tBLF4re
HXUZ6VqjIL0kOdYiWGAo8vL7bjgkJxWHMXBbSzyxGr7A3aTFh+/cMmRQSD8eyvuG
IqEi5CUE
=vh6h
-----END PGP SIGNATURE-----

--4Evn0R5nxrZ60pjO3BQ8cIuC6bl5sUEBj--


Acknowledgement sent to Dimitris <dimitris@stinpriza.org>:
Extra info received and forwarded to list. Copy sent to owner@bugs.devuan.org. Full text available.


Information forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#171; Package torsocks. Full text available.


bug reopened, originator not changed. Request was from KatolaZ <katolaz@freaknet.org> to control@bugs.devuan.org. Full text available.


Message received at 171@bugs.devuan.org:


Received: (at 171) by bugs.devuan.org; 9 Feb 2019 14:20:03 +0000
Date: Sat, 9 Feb 2019 15:14:09 +0100
From: KatolaZ <katolaz@freaknet.org>
To: 171@bugs.devuan.org
Subject: Please reopen


--66vujp27fgkzhr5b
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi,

I have re-opened the bug since you claim it still applies, but a bit
more information on what does not work on your side (or any other
report about similar incorrect behaviours by other users) would really
help.

HND

KatolaZ

--66vujp27fgkzhr5b
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iFwEABECAB0WIQSOWdaqRF79tKFTPVpfILOuC18GLwUCXF7gMQAKCRBfILOuC18G
L3Y8AJ4l8inF05lro7MHF0LNsASBYVM8YQCWJeCVEiuz8W1w9+cqLJaU3u4vxQ==
=OFuJ
-----END PGP SIGNATURE-----

--66vujp27fgkzhr5b--


Acknowledgement sent to KatolaZ <katolaz@freaknet.org>:
Extra info received and forwarded to list. Copy sent to owner@bugs.devuan.org. Full text available.


Information forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#171; Package torsocks. Full text available.


Message received at 171@bugs.devuan.org:


Received: (at 171) by bugs.devuan.org; 9 Feb 2019 09:00:01 +0000
Subject: Re: bug#171 acknowledged by developer (closing)
To: 171@bugs.devuan.org
From: Fulano Diego Perez <fulanoperez@cryptolab.net>
Date: Sat, 9 Feb 2019 19:55:57 +1100

Ticket closed without reason?


$ . torsocks on
Tor mode activated. Every command will be torified for this shell.
$ trans en:de+es+fr+it+pt 'Journalist and photographer at The Star
Newspaper'
1549702246 ERROR torsocks[23974]: Connection not allowed by ruleset (in
socks5_recv_connect_reply() at socks5.c:537)
1549702247 ERROR torsocks[23974]: Connection not allowed by ruleset (in
socks5_recv_connect_reply() at socks5.c:537)
1549702249 ERROR torsocks[23974]: Connection not allowed by ruleset (in
socks5_recv_connect_reply() at socks5.c:537)
1549702250 ERROR torsocks[23974]: Connection not allowed by ruleset (in
socks5_recv_connect_reply() at socks5.c:537)
1549702251 ERROR torsocks[23974]: Connection not allowed by ruleset (in
socks5_recv_connect_reply() at socks5.c:537)
1549702252 ERROR torsocks[23974]: Connection not allowed by ruleset (in
socks5_recv_connect_reply() at socks5.c:537)


ssh and sftp fail also

?





Devuan bug Tracking System wrote:
> This is an automatic notification regarding your bug report
> #171: torsocks: can't torify anymore,
> which was filed against the torsocks package.
> 
> It has been closed by one of the developers, namely
> KatolaZ <katolaz@freaknet.org>.
> 
> Their explanation is attached below.  If this explanation is
> unsatisfactory and you have not received a better one in a separate
> message then please contact the developer, by replying to this email.
> 
> Devuan Bugs Owner
> (administrator, Devuan bugs database)
> 
> Received: (at 171-done) by bugs.devuan.org; 1 Feb 2019 21:10:03 +0000
> Return-Path: <katolaz@freaknet.org>
> Delivered-To: devuanbugs@dyne.org
> Received: from tupac3.dyne.org [195.169.149.119]
> 	by fulcanelli with IMAP (fetchmail-6.3.26)
> 	for <debbugs@localhost> (single-drop); Fri, 01 Feb 2019 22:10:03 +0100 (CET)
> Received: from [127.0.0.1] (localhost [127.0.0.1])
> 	(Authenticated sender: katolaz@freaknet.org)
> 	with ESMTPSA id 3F5DBF60BA1
> Date: Fri, 1 Feb 2019 22:07:43 +0100
> From: KatolaZ <katolaz@freaknet.org>
> To: 171-done@bugs.devuan.org
> Subject: closing
> Message-ID: <20190201210743.rtsbpt34xs4klikg@katolaz.homeunix.net>
> MIME-Version: 1.0
> Content-Type: multipart/signed; micalg=pgp-sha1;
> 	protocol="application/pgp-signature"; boundary="3pazb5d24puaem3u"
> Content-Disposition: inline
> User-Agent: NeoMutt/20170113 (1.7.2)
> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED
> 	autolearn=disabled version=3.4.2
> X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org
> 
> 
> --3pazb5d24puaem3u
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> 
> Closing. Please reopen if this still applies.
> 
> --3pazb5d24puaem3u
> Content-Type: application/pgp-signature; name="signature.asc"
> 
> -----BEGIN PGP SIGNATURE-----
> 
> iF0EABECAB0WIQSOWdaqRF79tKFTPVpfILOuC18GLwUCXFS1HAAKCRBfILOuC18G
> LzRyAJ9Jbr3Avm85EGt4MXL5WXhrUlkkEACfUcbKudpHLQXWaKfSPhPVr0gLTcw=
> =RBz3
> -----END PGP SIGNATURE-----
> 
> --3pazb5d24puaem3u--
> 


Acknowledgement sent to Fulano Diego Perez <fulanoperez@cryptolab.net>:
Extra info received and forwarded to list. Copy sent to owner@bugs.devuan.org. Full text available.


Information forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#171; Package torsocks. Full text available.


Message received at 171-done@bugs.devuan.org:


Received: (at 171-done) by bugs.devuan.org; 1 Feb 2019 21:10:03 +0000
Date: Fri, 1 Feb 2019 22:07:43 +0100
From: KatolaZ <katolaz@freaknet.org>
To: 171-done@bugs.devuan.org
Subject: closing


--3pazb5d24puaem3u
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Closing. Please reopen if this still applies.

--3pazb5d24puaem3u
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQSOWdaqRF79tKFTPVpfILOuC18GLwUCXFS1HAAKCRBfILOuC18G
LzRyAJ9Jbr3Avm85EGt4MXL5WXhrUlkkEACfUcbKudpHLQXWaKfSPhPVr0gLTcw=
=RBz3
-----END PGP SIGNATURE-----

--3pazb5d24puaem3u--


Notification sent to Fulano Diego Perez <fulanoperez@cryptolab.net>:
bug acknowledged by developer. Full text available.


Reply sent to KatolaZ <katolaz@freaknet.org>:
You have taken responsibility. Full text available.


Message received at 171@bugs.devuan.org:


Received: (at 171) by bugs.devuan.org; 1 Feb 2019 20:30:05 +0000
To: 171@bugs.devuan.org
From: Dimitris <dimitris@stinpriza.org>
Subject: works
Date: Fri, 1 Feb 2019 22:28:01 +0200

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--CmIoz0QZSXyDwv2EH8Tyn9thNheIx4CwW
Content-Type: multipart/mixed; boundary="hVJzkLZ6PgTJc2BR7hIAj8TBXgiiHSkFK";
 protected-headers="v1"
From: Dimitris <dimitris@stinpriza.org>
To: 171@bugs.devuan.org
Message-ID: <dedfc35a-3408-00f0-7d36-d9deedee03a5@stinpriza.org>
Subject: works

--hVJzkLZ6PgTJc2BR7hIAj8TBXgiiHSkFK
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

i know this is old, but just FYI, reporting that  version 2.3.0-1
(beowulf) works ok. no problem using it as described or any other way.

never really had any issues with torsocks, even with ascii, IIRC.


--hVJzkLZ6PgTJc2BR7hIAj8TBXgiiHSkFK--

--CmIoz0QZSXyDwv2EH8Tyn9thNheIx4CwW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEECppUFUF7C9a+eth/9jQAR3Vpa4YFAlxUq9EACgkQ9jQAR3Vp
a4aK+BAAhQVf7zTmLYcBUFSI9b6tYBlsODVhnw6iJioyNYQ5ls2gTGGGQhgwSl3t
eOYfaF5grjbcvOL7vRoKu4KzUPyBXwbXeOmmIcBXvY5MITzyb3atUfYQ7I4saUQg
zn3wmLoYxAmK4v73fHIusM5kGQL9P3c66yNCLUnmPxCiDz+coEhrBkOBOjy2CZqc
/kOu5p390Wvxxy+56T5naVZD0RW/evhz0JD6LNCzraXrJHJ7b5WqeBlahIQ0hD04
SePJm6CpyFZ3RWW2NRRXfoBP+CjUVpyOx1vQ011870Ovvk8uHE/5MwKYgvL0w72k
AYUHu1NNaCKQkw4oNJy9p3rm/bKQrB0uJ7D2ojp9bJFYtqZ0+/rqag049G5N05VP
kVFr1oEXEz7RelRipx6OHT6v3QCfgSLCJdWqOM1TKmp6pJnVmhQLbpqBkSiR+Flf
/R5LdEruokrx0d/W1dKL02Q69KS82dfN1yjntoWu/ju2fC8c8pZkEdBn9uDJ4Fn4
xk6clp7ZaTyZkRZHQ43PY5LvYMbF/f1JPLqH067FLhvuOWL663K1ad1PY3Ummjyu
n8/53Y07/JrzdEDih3vWM2lnVzAbZVvspsIzR39GX0/wP/+5vFRdMdYVUW1Blw+c
XMh8GGAQk32HilAOgV+hKOdOm7segKP9JYyq+SUQdN9R27B7PkM=
=6vce
-----END PGP SIGNATURE-----

--CmIoz0QZSXyDwv2EH8Tyn9thNheIx4CwW--


Acknowledgement sent to Dimitris <dimitris@stinpriza.org>:
Extra info received and forwarded to list. Copy sent to owner@bugs.devuan.org. Full text available.


Information forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#171; Package torsocks. Full text available.


Tags removed: ascii Request was from KatolaZ <katolaz@freaknet.org> to control@bugs.devuan.org. Full text available.


Tags added: jessie, ascii Request was from OmegaPhil <OmegaPhil@startmail.com> to control@bugs.devuan.org. Full text available.


Message received at 171@bugs.devuan.org:


Received: (at 171) by bugs.devuan.org; 8 Jan 2018 06:10:02 +0000
To: 171@bugs.devuan.org
From: Fulano Diego Perez <fulanoperez@cryptolab.net>
Subject: torsocks: can't torify anymore
Date: Mon, 8 Jan 2018 17:01:42 +1100


syslog

Jan  8 localhost Tor[pid]: Your application (using socks5 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. Rejecting.


this applies to ascii also

can anybody confirm torsocks and ssh/sftp works for them ?




Acknowledgement sent to Fulano Diego Perez <fulanoperez@cryptolab.net>:
Extra info received and forwarded to list. Copy sent to owner@bugs.devuan.org. Full text available.


Information forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#171; Package torsocks. Full text available.


Message received at submit@bugs.devuan.org:


Received: (at submit) by bugs.devuan.org; 29 Dec 2017 06:20:04 +0000
Subject: torsocks: can't torify anymore
To: submit@bugs.devuan.org
From: Fulano Diego Perez <fulanoperez@cryptolab.net>
Date: Fri, 29 Dec 2017 17:16:47 +1100




Package: torsocks
Version: 2.0.0-3
Severity: normal


$ . torsocks on
Tor mode activated. Every command will be torified for this shell.

$ ssh -p 123 user@host -s sftp
[Dec 29 16:59:39] ERROR torsocks[6389]: Connection not allowed by
ruleset (in socks5_recv_connect_reply() at socks5.c:520)
ssh: connect to host host port 123: Software caused connection abort


$ sftp -P 123 user@host
ssh: Could not resolve hostname host: Name or service not known
Couldn't read packet: Connection reset by peer

used to work before





-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 1.0 (jessie)
Release:	1.0
Codename:	jessie
Architecture: x86_64

Kernel: Linux 3.16.0-4-amd64
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages torsocks depends on:
ii  libc6  2.19-18+deb8u10

Versions of packages torsocks recommends:
ii  tor  0.3.2.8-rc-1~d80.jessie+1

torsocks suggests no packages.

-- no debconf information


Acknowledgement sent to Fulano Diego Perez <fulanoperez@cryptolab.net>:
New bug report received and forwarded. Copy sent to owner@bugs.devuan.org. Full text available.


Report forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#171; Package torsocks. Full text available.


Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.

Devuan Bugs Owner <owner@bugs.devuan.org>.
Last modified: Tue, 17 Sep 2019 22:39:01 UTC