| Summary: | Konqueror (kio_http?) seems to bypass SOCKS | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | Verdi March <cincaipatron> |
| Component: | http | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | adawit |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
kio_http does not use SOCKS at all. Does not work for me either. The strange thing about this is that it _did_ work with KDE 3.3.2 (Debian sarge packages). Oh forgot to say, I'm using 3.5.2 (Ubuntu 6.06 LTS package 3.5.2-0ubuntu27). Ok, I found out that it was the fix of bug #101149 which removed SOCKS support from kio_http. Diff can be found here: http://websvn.kde.org/trunk/kdelibs/kioslave/http/http.cc?rev=396327&r1=394565&r2=396327 Unfortunately the new configuration entry ("Use global SOCKS settings") in the proxy setup dialog is still not present. I think the baby has been thrown out together with the water when fixing that bug: at the moment there's no way to use a SOCKS proxy with kio_http. I guess this is over 4 years late, but you can use a SOCKS server so long as you enter the socks address in the HTTP proxy input field as "socks://<hostname>". kio_http will then automatically use that to go through the socks proxy. No client configuration required such as dante client needed. More changes to the proxy configuration and use will be forth coming in the future releases of KDE. Thanks for the report. |
Version: (using KDE KDE 3.5.3) Installed from: SuSE RPMs I set KDE to use SOCKS (dante client is installed). The SOCKS server is actually an ssh server (connected using ssh -D 1080 remote_ssh_server). Programs such as Kopete and Kmail are correctly socksified; netstat shows that they open connections to localhost:1080. However, for Konqueror and Akregator, netstat shows that these two directly connect to remote sites. I presume that these programs bypass SOCKS? My /etc/socks.conf contains the followings: route { from: 0.0.0.0/0 to: 0.0.0.0/0 via: 127.0.0.1 port = 1080 protocol: tcp udp proxyprotocol: socks_v4 socks_v5 method: none } route { from: 0.0.0.0/0 to: . via: 127.0.0.1 port = 1080 protocol: tcp udp proxyprotocol: socks_v4 socks_v5 method: none }