-
Does the socksification fail with other executables?
What is the output of the following?: objdump -T /usr/lib/libtsocks.so.
2009-02-26 01:37:02 UTC in tsocks
-
The following is a revised and properly wrapped 106-line patch (metacharacters aside):
diff -ur tsocks-1.8beta5/tsocks.c tsocks-1.8/tsocks.c
--- tsocks-1.8beta5/tsocks.c 2008-08-24 08:47:43.156401152 -0400
+++ tsocks-1.8/tsocks.c 2008-08-24 08:48:26.968740664 -0400
@@ -99,6 +99,9 @@
static int read_socksv4_req(struct connreq *conn);
static int read_socksv5_connect(struct connreq...
2008-08-24 12:56:11 UTC in tsocks
-
The socket of the actual connect to the SOCKS server does not have to be in non-blocking mode just because the socket original connect was. Retaining the non-blocking mode of new connections seems to cause problems with some applications using the transparent SOCKS library.
Unfortunately, toggling non-blocking places the application at the mercy of the SOCKS server which might itself be...
2008-08-24 12:20:41 UTC in tsocks
-
The socket of the actual connect to the SOCKS server does not have to be in non-blocking mode just because the socket original connect was. Retaining the non-blocking mode of new connections seems to cause problems with some applications using the transparent SOCKS library.
Unfortunately, toggling non-blocking places the application at the mercy of the SOCKS server which might itself be...
2008-08-24 12:09:27 UTC in tsocks
-
Only for incomplete request states.
2008-08-24 11:30:52 UTC in tsocks
-
This earlier patch has a flaw that fails to restore non-blocking sockets to their original state after changing them to non-blocking. Please disregard it. I have created and updated a separate thread for the issue that this earlier patch was intended to address.
2008-08-16 20:14:12 UTC in tsocks
-
Unfortunately, toggling non-blocking places the application at the mercy of the SOCKS server which might itself be slower than expected cause everything to be sluggish. Whatever is causing the problem with "some" applications seems to be a bug in the application, not the library. Nevertheless, there may be a way to handle it through the library by acting upon calls to close a connection that is...
2008-08-16 20:04:17 UTC in tsocks
-
The socket of the actual connect to the SOCKS server does not have to be in non-blocking mode just because the socket original connect was. Retaining the non-blocking mode of new connections seems to cause problems with some applications using the transparent SOCKS library.
2008-08-08 19:26:28 UTC in tsocks
-
Better yet, consider applying the following 101-line patch (which I do not know how to attach to this tracker):
diff -ur tsocks-1.8beta5/tsocks.c tsocks-1.8/tsocks.c
--- tsocks-1.8beta5/tsocks.c 2008-08-08 14:28:40.134118960 -0400
+++ tsocks-1.8/tsocks.c 2008-08-08 15:08:27.266219720 -0400
@@ -775,6 +775,20 @@
conn->state);
switch(conn->state) {.
2008-08-08 19:11:50 UTC in tsocks
-
In the TSOCKS source code directory, create a file named configure.diff with the following 11-line contents:
--- configure- 2008-07-31 14:22:45.000000000 -0400
+++ configure 2008-07-31 14:34:23.000000000 -0400
@@ -2228,7 +2228,7 @@
echo $ac_n "checking for correct poll prototype""... $ac_c" 1>&6
echo "configure:2230: checking for correct poll prototype" >&5
PROTO=
-for testproto...
2008-07-31 19:07:01 UTC in tsocks
