[Pkg-anonymity-tools] Bug#684580: SIGSEGV in torsocks 2.0.0-1

[David Goulet]

On 03 Sep (08:17:26), JS wrote:
> I've attached text files with the bt full for midori and chromium.
> 

Hrm, unfortunately I can't get the exact call site since you are using I
suppose the package which does not provide debug symbol.

However, I think I understand what's going on here. In a nutshell, the
symbols that the preloaded library (libtorsocks.so) hijacks are
resolved. After that, the libc calls all library constructors in a
"unkwnown-unspecified" order where libGL.so ends up calling close() that
is resovled to tsocks_close() but segfaults when calling the original
libc close symbol because torsocks constructor has not yet been called
to it couldn't get the libc close() symbol

This is a very difficult issue with dlopen() in constructor since the
libc does not guarantees on constructor call ordering...

There are solutions to that issue, I need to investiguate more and do
some testing. I will open a bug on the upstream tracker because this is
not a Debian specific issue.

Thanks!
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-anonymity-tools/attachments/20140910/53d8806b/attachment.sig>