Version: 0.7.1 (using KDE 3.1.2) Installed from: compiled sources Compiler: gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98) OS: Linux (i686) release 2.4.7-10 I need to use SOCKS5 proxy server for any connection to non-HTTP Internet (Jabber, ICQ, IRC). But only Jabber has appropriate setting. Why I can use IRC/ICQ? Run kopete through Dante has actuate segfault. I guess, kopete must has separate tab or better profile for connection via proxy server. And each account record must has choice for use proxy connection or not.
*** Bug 58274 has been marked as a duplicate of this bug. ***
*** Bug 57843 has been marked as a duplicate of this bug. ***
Leaving this one in Bugzilla and not the (older) reports that I just marked as duplicate because this one is generic and the others are per-plugin. This should be solved mostly at the kdelibs level (i.e. it's almost unfixable for now), but the rest is libkopete's work, not the various plugins'. Martijn
As long as we are using the various backend plugins I am not sure if this can be done in a generic way at all. They'd all have to be based on KExtendedSocket (or wherever the Proxy handling goes), can this be done with our code base? I know that it will be possible with Jabber once libxmpp has stabilized, the same goes probably for Oscar. What about Yahoo and Gadu-Gadu?
I join to Till Gerken and want to use IRC and ICQ via SOCKS5!
Implementation-wise, sure. But the config settings should move to libkopete just like they already did in 0.7.x for the password editbox in the account config. Martijn
Alright, that makes sense. Something for the todo list for the next version.
Although I didn't say so in bug 57843, I don't have a SOCKS5 proxy at work, I only have an HTTP proxy, which is how we currently get GAIM to connect out to the net. Does this bug include the standardization of non-SOCKS5 proxies as well?
Non-SOCKS5 proxies won't be standardised before KDE 3.2. I'm working on the implementation, but don't get your hopes up.
Just to let you know, I've got preliminary HTTP proxy support working for the KDE 3.3 framework.
*** Bug 68545 has been marked as a duplicate of this bug. ***
I think kopete needs a proxy support to get more users use it.
Giovanni: we know it. But I don't have the time to write the code any time soon, even though the most part is already there. What is missing is the UI and the code to decide what proxy to use for which servers. That's not a high priority and will probably not be implemented until KDE 4 (Kopete 1.0).
*** Bug 131348 has been marked as a duplicate of this bug. ***
Using a common set of socket classes would be a start.
Should this bug be tagged as duplicate for #74832 ?
SOCKS5 and HTTP proxying are not the same.