GPG keyserver access does not work behind a proxy
Bug #733023 reported by
Olaf Meeuwissen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| jockey (Ubuntu) |
Fix Released
|
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).
Revision history for this message
| Olaf Meeuwissen (olaf.meeuwissen) wrote | #1 |
Revision history for this message
| Martin Pitt (pitti) wrote | #2 |
| Changed in jockey (Ubuntu): | |
| assignee: | nobody → Martin Pitt (pitti) |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in jockey (Ubuntu): | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Olaf Meeuwissen (olaf.meeuwissen) wrote | #4 |
To post a comment you must log in.
That looks correct to me, thanks! It passes the tests as well, committed to trunk.