[Bug 824091] [NEW] ssl through proxy broke between 4.6 and 4.7
Launchpad Bug Tracker
824091 at bugs.launchpad.net
Thu Dec 15 19:56:39 UTC 2011
You have been subscribed to a public bug:
I use ssh -D to create a SOCKS5 proxy and drive all of my network
traffic through it. I use a .pac file to configure this and set KDE to
use it through the system settings.
e.g. ssh -D 8080 user at my.domain establishes the proxy, and the proxy.pac
file configures the exceptions (local network, etc.).
I also have a DAViCal server on that same server. I access it through
https://firstname.lastname@example.org/blahblah and with the standard Kubuntu
packages it worked fine.
cal.my.domain has the same IP as the ssh server I am connecting to to
establish the SOCKS5 proxy.
Upon upgrading to 4.7 through the kubuntu backports PPA this broke. For
some reason KDE cannot establish an SSL connection to the server through
the socks5 proxy. I had to add a specific exception such that the proxy
is not used to connect to my davical server (which is also the socks5
I'm not sure if KDE 4.6 did it right, or if 4.7 is doing it right and
the exception is really what should be done, but I'm posting this bug
report so that it can be evaluated.
** Affects: kubuntu-meta (Ubuntu)
ssl through proxy broke between 4.6 and 4.7
You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu.
More information about the kubuntu-bugs