GPG keyserver access does not work behind a proxy

Bug #733023 reported by Olaf Meeuwissen on 2011-03-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Medium
Martin Pitt

Bug Description

This is related to the automatic printer driver download functionality (see also #729185).

After getting the GPG fingerprint successfully, jockey may need to contact a GPG keyserver to fetch the corresponding key. During our testing we have noticed that jockey's GPG support does not take the environment's http_proxy setting into account. This setting (as well as https_proxy) is taken into account in the other jockey components so we expected it to be used in this step as well. Hope this can be fixed.

We have a simple patch (attached) but haven't tested some corner cases yet (variable not set, variable empty).

Martin Pitt (pitti) wrote :

That looks correct to me, thanks! It passes the tests as well, committed to trunk.

Changed in jockey (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → Medium
status: New → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jockey - 0.9.2-0ubuntu3

---------------
jockey (0.9.2-0ubuntu3) natty; urgency=low

  * Merge from trunk:
    - OSLib.import_gpg_key(): Respect $http_proxy. Thanks Olaf Meeuwissen.
      (LP: #733023)
    - oslib.py: Switch to default keyserver on port 80 to be more proxy
      friendly. (LP: #733029)
 -- Martin Pitt <email address hidden> Fri, 11 Mar 2011 18:07:01 +0100

Changed in jockey (Ubuntu):
status: Fix Committed → Fix Released

We've tested with the above version. Works like a charm. Thanks.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers