| Summary: | SOCKS Proxy support broken | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Ritesh Raj Sarraf <kde-bugs> |
| Component: | general | Assignee: | Dawit Alemayehu <adawit> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ebrahim, kde, xavier.gnata |
| Priority: | NOR | ||
| Version: | 4.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.8 | |
| Sentry Crash Report: | |||
Do you see this bug incomplete? I have been seeing this bug consistently. Konq is broken. Other web browsers work fine because others don't have the exclusion list. Same issue with konqueror 4.4.2. AFAICS, there is no SOCKS proxy support at all in kde4.X. Is there any plan for adding SOCKS proxy support to KDE? In KDE 4.7, this will be fixed. For now, you can try to enter socks://<proxy-address> into the protocol specific (HTTP) address box and see if that works for you. This looks like most a duplicate of #189019 and #147340, but there is different hints and information in the bugs. See https://bugs.kde.org/show_bug.cgi?id=189019#c31 for how to set SOCKS address in KDE 4.7 and up. For KDE 4.8, you will be able to set SOCKS proxy settings using the proxy configuration dialog once https://git.reviewboard.kde.org/r/102802/ is submitted. Git commit f90f318f2162df18a08b889d24ae8bbeab3b834c by Dawit Alemayehu. Committed on 01/08/2011 at 07:44. Pushed by adawit into branch 'master'. Rewrote the proxy configuration dialog to include missing SOCKS proxy entry and make it much simpler to use. BUG:82352 BUG:115704 BUG:139789 BUG:147340 BUG:164460 BUG:189019 BUG:190149 BUG:190901 BUG:205594 BUG:258196 BUG:283226 FIXED-IN:4.8 REVIEW: 102802 GUI: Proxy configuration dialog rewrite. M +0 -5 konqueror/settings/kio/CMakeLists.txt D +0 -251 konqueror/settings/kio/envvarproxy.ui D +0 -310 konqueror/settings/kio/kenvvarproxydlg.cpp D +0 -71 konqueror/settings/kio/kenvvarproxydlg.h D +0 -496 konqueror/settings/kio/kmanualproxydlg.cpp D +0 -86 konqueror/settings/kio/kmanualproxydlg.h M +410 -215 konqueror/settings/kio/kproxydlg.cpp M +30 -18 konqueror/settings/kio/kproxydlg.h M +833 -248 konqueror/settings/kio/kproxydlg.ui D +0 -79 konqueror/settings/kio/kproxydlgbase.cpp D +0 -69 konqueror/settings/kio/kproxydlgbase.h M +77 -88 konqueror/settings/kio/ksaveioconfig.cpp M +28 -32 konqueror/settings/kio/ksaveioconfig.h D +0 -291 konqueror/settings/kio/manualproxy.ui http://commits.kde.org/kde-baseapps/f90f318f2162df18a08b889d24ae8bbeab3b834c Dawit, you are a hero! |
Version: (using KDE 4.3.0) OS: Linux Installed from: Debian testing/unstable Packages I'm trying to bypass my firewall using ssh. Here's what I'm following from ssh: -D [bind_address:]port Specifies a local “dynamic” application-level port forwarding. This works by allocating a socket to listen to port on the local side, optionally bound to the specified bind_address. Whenever a connection is made to this port, the connec‐ tion is forwarded over the secure channel, and the application protocol is then used to determine where to connect to from the remote machine. Currently the SOCKS4 and SOCKS5 protocols are supported, and ssh will act as a SOCKS server. Only root can forward privileged ports. Dynamic port forwardings can also be specified in the configuration file. IPv6 addresses can be specified with an alternative syntax: [bind_address/]port or by enclosing the address in square brackets. Only the superuser can forward privileged ports. By default, the local port is bound in accordance with the GatewayPorts setting. However, an explicit bind_address may be used to bind the connection to a specific address. The bind_address of “localhost” indicates that the listening port be bound for local use only, while an empty address or ‘*’ indicates that the port should be available from all interfaces. Then I configured konqueror to use proxy by selecting the "Manually specify a proxy server". When I try to browse a website, it fails. The requested operation could not be completed Connection to Server Refused Unknown error I know ssh is doing the job properly because I have a locally compiled rekonq installed and it works there.