Hi David,
unfortunately, the fix for #766306 (fd passing) makes torsocks fail to
build on kfreebsd-{amd64,i386}:
https://buildd.debian.org/status/package.php?p=torsocks
May you please have a look?
Time-wise, I'd like to see this bug fixed in Jessie, and the deadline
to have a fix for an
Please reply on #768140, sorry for the confusion.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Control: severity -1 important
Control: tag -1 + pending
Hi,
David Goulet wrote (23 Oct 2014 13:15:02 GMT) :
On reason it might fail, this test needs Tor access thus the Internet
:).
Indeed, that was it -- thanks! The test passes for me when I give
network access to my pbuilder build
Hi David,
David Goulet wrote (22 Oct 2014 21:06:16 GMT) :
Just pushed the update in the upstream git.
https://gitweb.torproject.org/torsocks.git/commit/eb80d5cd10d10158b39c344ad035afe8d31a899f
That commit *improves* drastrically Unix socket fd passing detection and
adds a test also.
I've
On 23 Oct (08:02:36), intrigeri wrote:
Hi David,
David Goulet wrote (22 Oct 2014 21:06:16 GMT) :
Just pushed the update in the upstream git.
https://gitweb.torproject.org/torsocks.git/commit/eb80d5cd10d10158b39c344ad035afe8d31a899f
That commit *improves* drastrically Unix socket fd
Hi David,
tester wrote (22 Oct 2014 04:08:42 GMT) :
I was running bitmessage, and figured out it really isnt using the proxy, so I
ran it using torsocks, it ran for along time, but then crashed with this error
after I posted a message
ERROR torsocks[13827]: [recvmsg] Inet socket passing
On 22 Oct (11:07:02), intrigeri wrote:
Hi David,
tester wrote (22 Oct 2014 04:08:42 GMT) :
I was running bitmessage, and figured out it really isnt using the proxy,
so I
ran it using torsocks, it ran for along time, but then crashed with this
error
after I posted a message
ERROR
Hi,
David Goulet wrote (22 Oct 2014 13:22:14 GMT) :
Yes. That means torsocks detected that the torified process received an
inet socket from an other process using the fd passing feature of Unix
socket thus stopped everything since it can't torify that socket.
Thanks for the explanation :)
On 22 Oct (16:29:28), intrigeri wrote:
Hi,
David Goulet wrote (22 Oct 2014 13:22:14 GMT) :
Yes. That means torsocks detected that the torified process received an
inet socket from an other process using the fd passing feature of Unix
socket thus stopped everything since it can't torify
David Goulet wrote (22 Oct 2014 14:42:14 GMT) :
In a nutshell, cleanup the received socket and return EACCESS?
If we agree on that, I can push a patch today!
I'm lacking the basic knowledge needed to clearly understand
everything about this proposal, but your reasoning looks sensible,
so... go!
On 22 Oct (17:01:29), intrigeri wrote:
David Goulet wrote (22 Oct 2014 14:42:14 GMT) :
In a nutshell, cleanup the received socket and return EACCESS?
If we agree on that, I can push a patch today!
I'm lacking the basic knowledge needed to clearly understand
everything about this proposal,
David Goulet wrote (22 Oct 2014 15:19:58 GMT) :
I guess you prefer an official release for that?
A commit applied to your HEAD would be enough, as long as it's
well tested.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
On 22 Oct (22:29:43), intrigeri wrote:
David Goulet wrote (22 Oct 2014 15:19:58 GMT) :
I guess you prefer an official release for that?
A commit applied to your HEAD would be enough, as long as it's
well tested.
Just pushed the update in the upstream git.
Package: torsocks
Version: 2.0.0-1
Severity: normal
Dear Maintainer,
I was running bitmessage, and figured out it really isnt using the proxy, so I
ran it using torsocks, it ran for along time, but then crashed with this error
after I posted a message
ERROR torsocks[13827]: [recvmsg] Inet socket
14 matches
Mail list logo
