Hi, I'm using Kopete 4.2.2 from Debian Unstable. My desktop is using KDE 4.2.2 and it's rocking stable and awesome. I've been searching how to setup Kopete to use proxy. All I ever have is only a clue to setup Dante + Tor without proper explanation about it. I believe it was for Kopete in 0.12.x.

I'm willing to sacrifice my desktop system to use vodoo magic of "./configure && make && make" instead of _apt-get_. I'm also willing to setup a cannon to kill a fly. So, please, kind ladies/gentlemens, tell me how to setup Kopete using proxy. Is there a patch?

I refuse to use the "apt-get install pidgin" -- no flame intended just want to make sure all of my apps are pure Qt. But, if that's the way to go, can't helped it. :'(

Sorry for my bad English.

jpmrblood wrote:I'm willing to sacrifice my desktop system to use vodoo magic of "./configure && make && make" instead of _apt-get_.

If so... you can use proxychains. I use it to organize usage of kopete from KDE3 behind the squid firewall in my network.

pavel wrote:

jpmrblood wrote:I'm willing to sacrifice my desktop system to use vodoo magic of "./configure && make && make" instead of _apt-get_.

If so... you can use proxychains. I use it to organize usage of kopete from KDE3 behind the squid firewall in my network.

I've googled and try using proxychains from Debian. However, it didn't connect. Here's the output:

[php]$ proxychains kopete
kopete(18043): Communication problem with "kopete" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, themessage bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "[/php]

This is what I do:
- I have choose random, strict, dynamic chain and lastly commented all.
- I set 1 HTTP proxy (a Squid proxy) in my list.
- comment and uncomment and change the chain_len value.

Still no luck. Where did I do wrong? Would you like to show a bit of your config? Thx.

I have this output by using Kopete from kde 4.2.2 through proxychains, thar really connected to the jabber server:

Code: Select all

pavel@rzn-sepak-bpa:~/log> proxychains kopete
ProxyChains-3.1 (http://proxychains.sf.net)
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
kopete(9499)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '!
Calling appendChild() on a null node does nothing.
|S-chain|--10.47.0.75:8080--81.18.129.4:443--OK
kopete(9499): Attempt to use QAction "show_participants_widget" with KXMLGUIFactory!
Enchant dict for "ru" 0x879c568

pavel@rzn-sepak-bpa:~/log>


Note the string with S-chain
My working configuration is

Code: Select all

pavel@rzn-sepak-bpa:~> cat /etc/proxychains.conf | grep -v "^#" | grep -v "^$"
strict_chain
tcp_read_time_out 15000
tcp_connect_time_out 8000
[ProxyList]
http    10.47.0.75      8080
pavel@rzn-sepak-bpa:~>


pavel wrote:

Code: Select all

pavel@rzn-sepak-bpa:~> cat /etc/proxychains.conf | grep -v "^#" | grep -v "^$"
strict_chain
tcp_read_time_out 15000
tcp_connect_time_out 8000
[ProxyList]
http    10.47.0.75      8080
pavel@rzn-sepak-bpa:~>


I'm sorry for late reply, I'm off from my PC on weekend. :P

Anyway, thanks for the proxychains version. Debian uses proxychains version 2.1 while yours 3.1 and I think that's the reason of the previous attempt. Now I have compiled the 3.1 and runs it. Btw, I'm trying to connect to Y!M. In my account preference, I've set these:
Server : scs.msg.yahoo.com
Port : 80 / 5050 (tried both)

Here's the snippet:

Code: Select all

$  proxychains kopete
kopete(12141) Kopete::AccountManager::setOnlineStatus: category:  2
kopete(12141) Kopete::AccountManager::setOnlineStatus: category:  2
Object::connect: No such signal ClientStream::disconnected()
Object::connect:  (receiver name: 'yahooclient')
|S-chain|--192.168.45.99:8080--66.163.181.175:5050--192.168.45.99:8080--66.163.181.174:5050-<--denied


My associates that use original Y!M and Pidgin can connect, so I don't think the proxy is the issue. Or have I miss something?

jpmrblood wrote:I'm sorry for late reply, I'm off from my PC on weekend. :P

Do not worry. Mine was off too

jpmrblood wrote:Btw, I'm trying to connect to Y!M. In my account preference, I've set these:
Server : scs.msg.yahoo.com
Port : 80 / 5050 (tried both)

I do not use YIM. I use ICQ and Jabber/XMPP over proxy. Try it for an experiment.

People on different Russian forums say that the denied word in the proxychains log means denying on the proxy. So... look at proxy's logs... if you can. Otherwose, you can try opening the destination port in browser. I tried
https://jabber.nnov.net:5222
https://jabber.nnov.net:443
The first was denied and the second passed.

jpmrblood wrote:My associates that use original Y!M and Pidgin can connect, so I don't think the proxy is the issue. Or have I miss something?

Maybe, they are using http-pooling. In http-pooling they connect with GET and PUT http methods. Proxychains uses onlu CONNECT method. In most restrictive networks, CONNECT to ports other than 443 (https) is denied.

That is why you are to test your connection in browser through https instead of http. Https tries to CONNECT, http tries to GET and PUT.

As for me, I had to connect to jabber server to port 443 because of the same reason.

pavel wrote:People on different Russian forums say that the denied word in the proxychains log means denying on the proxy. So... look at proxy's logs... if you can. Otherwose, you can try opening the destination port in browser. I tried
https://jabber.nnov.net:5222
https://jabber.nnov.net:443
The first was denied and the second passed.

Maybe, they are using http-pooling. In http-pooling they connect with GET and PUT http methods. Proxychains uses onlu CONNECT method. In most restrictive networks, CONNECT to ports other than 443 (https) is denied.

As for me, I had to connect to jabber server to port 443 because of the same reason.

I guess our proxy doesn't welcome CONNECT method other than port 443.

Is there a way to make proxychains uses GET or POST instead?

jpmrblood wrote:Is there a way to make proxychains uses GET or POST instead?

As I know - no. Try to use port 443 to bind to your server. Maybe, it listens to 443 too.

Code: Select all

This version (3.x) introduces support for DNS resolving through proxy
it supports SOCKS4, SOCKS5 and HTTP CONNECT proxy servers.
Auth-types: socks - "user/pass" , http - "basic".


As it demands HTTP CONNECT proxy, I think it works over HTTP CONNECT session.

pavel wrote:

jpmrblood wrote:Is there a way to make proxychains uses GET or POST instead?

As I know - no. Try to use port 443 to bind to your server. Maybe, it listens to 443 too.

Yes, I have tried this, but it seems that Yahoo! doesn't use this port. CMIIW.

pavel wrote:

Code: Select all

This version (3.x) introduces support for DNS resolving through proxy
it supports SOCKS4, SOCKS5 and HTTP CONNECT proxy servers.
Auth-types: socks - "user/pass" , http - "basic".


As it demands HTTP CONNECT proxy, I think it works over HTTP CONNECT session.

What if I have my own proxy server in my computer that uses CONNECT to our proxy server. Is there a solution exists such as that?

jpmrblood wrote:What if I have my own proxy server in my computer that uses CONNECT to our proxy server. Is there a solution exists such as that?

Do not think so. In HTTP CONNECT you are able to create connection and wait for incoming traffic. In HTTP PUT or GET you can only request the information from the server side - there would be no ineraction in the session.

Hello guys

I have the same problem here, and I hope if you can help me

My proxy configuration looks like this

Code: Select all

[ProxyList]
# add proxy here ...
http   http://cache-1.in.crous-toulouse.fr   3128


and I have this error message

Code: Select all

mikesol@linux-zfbi:~> proxychains kopete
ProxyChains-3.1 (http://proxychains.sf.net)
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
mikesol@linux-zfbi:~> Calling appendChild() on a null node does nothing.


And if I try to connect into my gmail or hotmail account this happens

Unknown signature value: 795
|S-chain|-<>-127.0.0.1:9050-<--timeout
|S-chain|-<>-127.0.0.1:9050-<--timeout
|S-chain|-<>-127.0.0.1:9050-<--timeout
|S-chain|-<>-127.0.0.1:9050-<--timeout
|S-chain|-<>-127.0.0.1:9050-<--timeout
|S-chain|-<>-127.0.0.1:9050-<--timeout
|S-chain|-<>-127.0.0.1:9050-<--timeout
|S-chain|-<>-127.0.0.1:9050-<--timeout
|S-chain|-<>-127.0.0.1:9050-<--timeout
|S-chain|-<>-127.0.0.1:9050-<--timeout
|DNS-request| messenger.hotmail.com
|S-chain|-<>-127.0.0.1:9050-<--timeout
|DNS-response|: messenger.hotmail.com is not exist

I am not an expert in these things, so anyone can help to configuring it correctly?

Thanks in advance

Code: Select all

#        Examples:
#
#               socks5  192.168.67.78   1080    lamer   secret
#               http    192.168.89.3    8080    justu   hidden
#               socks4  192.168.1.49    1080
#               http    192.168.39.93   8080


So... I think you should place

Code: Select all

http   http://cache-1.in.crous-toulouse.fr   3128

instead

Code: Select all

http   http://cache-1.in.crous-toulouse.fr   3128

The errors ypu are recieving are not generated by proxychains, I think. It should be from Kopete.

in S-chain log string you whould see the try to connect to your proxy. If not, proxychains is not configured properly.

And that is hy your Kopete connects to your 127.0.0.1:9050 insread of proxy (look at my proxychains log above).

Kopete uses KIO, thus running Kopete under proxychains isn't going to work. You need to run the entire of KDE under proxy chains, or alternately, the settings in System Settings > Network Settings > Proxy may be sufficient.

The process in particular that needs to run under proxychains is "klauncher"

bcooksley wrote:Kopete uses KIO, thus running Kopete under proxychains isn't going to work.

Kopete does work through proxychains. I have it working on my LAN on 3 workstations.

bcooksley wrote:You need to run the entire of KDE under proxy chains, or alternately, the settings in System Settings > Network Settings > Proxy may be sufficient.

I have not found how to make Kopete use system-wide settings to connect to Squid HTTP-connect proxy (it ignores KDE proxy server settings). It has not been working in KDE3 and KDE 4.3.2. If it was possible, this topic would be unneeded.

So... Is it possible to proxy Kopete trough HTTP-Connect proxy-server now? If so... than - how?

Seems like Kopete rolls its own, which is why it works under Proxychains, and alse ignores KDE wide settings.