1 |
On Tuesday 15 May 2012 22:08:17 you wrote: |
2 |
> On Tue, 15 May 2012 16:57:26 +0100 |
3 |
> Mick <michaelkintzios@×××××.com> wrote: |
4 |
|
5 |
> > I am not sure if the problem is related to the tsocks LD_PRELOAD |
6 |
> > error. |
7 |
> |
8 |
> It almost certainly is, tsocks uses LD_PRELOAD to mangle it's magic so |
9 |
> that stuff works. I believe chromium has severe issues with tsocks |
10 |
> because of how it does it's sandboxing, but I honestly don't know how |
11 |
> to get around that. |
12 |
> |
13 |
> On a properly setup Gentoo amd64 system, /lib is a link to /lib64, so |
14 |
> the error you get is not a path error, the chromium binary really |
15 |
> cannot (or will not) deal with tsocks.so |
16 |
> |
17 |
> I don't see anything wrong with the rest of your config. I honestly |
18 |
> think you are dealing with a chromium feature not a chromium bug. |
19 |
> |
20 |
> Have you searched chromium-specific sites to see what others have to |
21 |
> say? |
22 |
|
23 |
I haven't yet, because it is not just Chromium that's not working as it is |
24 |
supposed to (although it is the most vocal app on the terminal when called |
25 |
with tsocks). I haven't yet found an app which will work with tsocks at all. |
26 |
|
27 |
The fact that proxychains does not work at all (applications completely ignore |
28 |
it and run outside the tunnel) made me question the sanity of my set up. Is |
29 |
there anything other than coincidence that would cause both apps to fail? |
30 |
-- |
31 |
Regards, |
32 |
Mick |