GNOME Bugzilla – Bug 578309
can't sync when only socks-proxy is configured.
Last modified: 2013-07-03 11:17:57 UTC
Please describe the problem: seahorse can't access key servers over HTTP (hkp://) when only SOCKS proxy is configured in gnome-network-properties. I have no means to try with an HTTP proxy configured. Error message (for each hkp:// key server with respective change host:port) is as follows: "Couldn't communicate with server 'pgp.mit.edu:11371': Cannot resolve proxy hostname" This does _not_ happen for LDAP key servers (ldap://). I have System -> Preferences -> Network Proxy in Gnome ('gnome-network-properties') configured to: (*) Manual proxy configuration Socks host: 10.83.30.1 Port: 1080 "Use the same proxy for all protocols" is _unchecked_. Other proxy addresses are blank with "Port: 0" (blank turns to zero). ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: seahorse 2.26.0-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse Uname: Linux 2.6.28-11-generic i686 Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information: Reported on Launchpad: https://bugs.launchpad.net/bugs/355050
Does this relate to "Bug 553269 – gnome proxy settings : socks doesn't work"? http://bugzilla.gnome.org/show_bug.cgi?id=553269 For me, who filed this bug at Ubuntu's Launchpad, Firefox uses the system settings for the Gnome-proxy. But that's not Gnome software so perhaps they use another - working - method to retrieve proxy settings? Which means there would be a bug in Gnome-implementations for using the Network Proxy configuration. Someone who knows more on the matter should have a say :)
Seahorse has only been set up to work with the http proxy IIRC.
I can confirm with seahorse 3.9.1
We now use libsoup's proxy implementation for HKP. So this should be solved in seahorse 3.9.2 *** This bug has been marked as a duplicate of bug 682495 ***
(In reply to comment #4) > We now use libsoup's proxy implementation for HKP. So this should be solved in > seahorse 3.9.2 > > *** This bug has been marked as a duplicate of bug 682495 *** Stef, I checked patch on bug 682495 against this report and it won't solve the problem. The reason, I think, is that we are not yet instructing in soup that the HTTP protocol has to go through SOCKS. Not sure though, since I didn't devote enough time, but I think work is still to be done for SOCKS redirection to work with HKP. In any case, I think this bug would be still valid for 3.9.2.
(In reply to comment #5) > In any case, I think this bug would be still valid for 3.9.2. Please test it. And if it's the case, please reopen the bug.
(In reply to comment #6) > (In reply to comment #5) > > In any case, I think this bug would be still valid for 3.9.2. > > Please test it. And if it's the case, please reopen the bug. ... I already did. The report is still valid. But the combo to change bug's status is not shown to me. I cannot reopen (?).
>The reason, I think, is that we are not yet instructing >in soup that the HTTP protocol has to go through SOCKS. This is fixed for me in Gnome 3.8 (Fedora 19)
Christian, yes it seems like it should be. Andres, could you provide me (perhaps privately) with a socks proxy that I could test this against, as well as instructions to reproduce?
(In reply to comment #9) > Christian, yes it seems like it should be. > > Andres, could you provide me (perhaps privately) with a socks proxy that I > could test this against, as well as instructions to reproduce? ... This is working now to me. It seems my distro upgraded my seahorse package without me noticing and I was trying with a version without bug 682495 patch :( Sorry for the mess ... You can try with a SOCKS redirection through SSH. $ ssh -D 8000 <some_server> Then, in GNOME proxy settings just change the mode to "Manual" and clean all the fields but the "Socks Host". Just fill with "localhost" and "8000". You can check the redirection is working with Epiphany, for example, which uses libsoup. Just go to: http://www.tracemyip.org/
(In reply to comment #10) > (In reply to comment #9) > > Christian, yes it seems like it should be. > > > > Andres, could you provide me (perhaps privately) with a socks proxy that I > > could test this against, as well as instructions to reproduce? > ... > > This is working now to me. > > It seems my distro upgraded my seahorse package without me noticing and I was > trying with a version without bug 682495 patch :( No problems. Thanks for testing again.