From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Socks-ifying an application
Date: Tue, 15 May 2012 16:57:26 +0100 [thread overview]
Message-ID: <CAGOe-eyqfqFH4fh6yYQSc91Q7BpAJuAJHgYakBxK6OkbO7wzbA@mail.gmail.com> (raw)
In-Reply-To: <20120515164557.5b18a56c@khamul.example.com>
On 15 May 2012 15:45, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Tue, 15 May 2012 10:50:43 +0100
> Mick <michaelkintzios@gmail.com> wrote:
>> $ ssh -D localhost:12465 root@10.10.10.12
>
> This part is fine.
>
> I tried the next part. It didn't work nicely for me.
Ah, thanks for this! It's reassuring to know that it's not just my system. :-)
> So what I do now is:
>
> Firefox + FoxyProxy
Firefox is less of a problem for me because I can set it up to
socksify everything. It is Kmail that I am mostly interested in.
> I see recent KDE now also supports socks. This is a nice new addition
> so konqueror can also use it.
Yes, but it does not work with the current stable kmail. The new
KDEPIM is such a nightmare I do not plan moving to it anytime soon.
It screwed up one box that I tried it on and that's enough for me.
:-(
Did you have any success with proxychains?
I am not sure if the problem is related to the tsocks LD_PRELOAD error.
I also noticed that when I try to set up a proxy server in Chromium
using the 'under the bonnet' tab, I get this:
"When running Chromium under a supported desktop environment, the
system proxy settings will be used. However, either your system is not
supported or there was a problem while launching your system
configuration.
But you can still configure via the command line. Please see man
chromium-browser for more information on flags and environment
variables."
Trying the command line did not fix it:
[4742:4753:1575546819:ERROR:object_proxy.cc(239)] Failed to call
method: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.NetworkManager was not provided by any .service files
That's what made me think that something on my system is not set up
properly. :-/
These are the libtsocks.so files in my system:
# ls -la /lib*/libtsocks.so
lrwxrwxrwx 1 root root 14 May 13 15:34 /lib/libtsocks.so -> libtsocks.so.1
lrwxrwxrwx 1 root root 14 May 13 15:34 /lib64/libtsocks.so -> libtsocks.so.1
# ls -la /lib/libtsocks.so*
lrwxrwxrwx 1 root root 14 May 13 15:34 /lib/libtsocks.so -> libtsocks.so.1
lrwxrwxrwx 1 root root 16 May 13 15:34 /lib/libtsocks.so.1 ->
libtsocks.so.1.8
-rwxr-xr-x 1 root root 42912 May 13 15:34 /lib/libtsocks.so.1.8
# ls -la /lib64/libtsocks.so*
lrwxrwxrwx 1 root root 14 May 13 15:34 /lib64/libtsocks.so -> libtsocks.so.1
lrwxrwxrwx 1 root root 16 May 13 15:34 /lib64/libtsocks.so.1 ->
libtsocks.so.1.8
-rwxr-xr-x 1 root root 42912 May 13 15:34 /lib64/libtsocks.so.1.8
I can't see why it would not load it, unless it should be trying to
load the '/lib64/libtsocks.so' instead of the '/lib/libtsocks.so' on
an amd64 system? Shall I file a bug?
--
Regards,
Mick
next prev parent reply other threads:[~2012-05-15 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 9:50 [gentoo-user] Socks-ifying an application Mick
2012-05-15 14:45 ` Alan McKinnon
2012-05-15 15:57 ` Mick [this message]
2012-05-15 21:08 ` Alan McKinnon
2012-05-15 22:19 ` Mick
2012-05-16 10:01 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGOe-eyqfqFH4fh6yYQSc91Q7BpAJuAJHgYakBxK6OkbO7wzbA@mail.gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox