Ignores $http_proxy setting

Bug #944367 reported by Soren Hansen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ssh-import-id (Ubuntu)
Fix Released
Wishlist
Dustin Kirkland 
Precise
Fix Released
Wishlist
Dustin Kirkland 

Bug Description

Lately, I find myself stuck behind proxies more often than I'm used to. ssh-import-id unfortunately ignores the commonly used http_proxy environment variable. wget understands it, so it's just a matter of not cleaning it from the environment before calling wget.

Matt Fischer (mfisch)
Changed in ssh-import-id (Ubuntu):
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Soren Hansen (soren) wrote :

Sorry, since it's https, the relevant environment variable is https_proxy, obviously.

Revision history for this message
Soren Hansen (soren) wrote :

Actually, I have to wonder why the environment is cleaned at all before calling wget?

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Soren, that was Jamie's suggestion. I've added him here, in case he can answer that one....

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I suggested it because importing a key is a sensitive operation. I maintain this is a sane default, but it seems it would make sense to add an optional command line argument to preserve https_proxy for when the user knows things are ok.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

I would be inclined to just whitelist the https_proxy environment variable, using env -i https_proxy="$https_proxy". However, Jamie's not on board with that at this time (per IRC).

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

<kirkland> jdstrand: so what would the call look like, for example? ssh-import-id -e https_proxy jdstrand soren kirkland ?
<kirkland> jdstrand: where -e says "enable this environment variable"
<kirkland> jdstrand: and https_proxy is the env variable to whitelist?
<jdstrand> kirkland: seems fine. alternatively you could always use wget with '--no-proxy' unless the user gives '-p' or '--use-proxy' to ssh-import-id

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Fix committed and released upstream. I'd like to see this make it into Precise too.

Changed in ssh-import-id (Ubuntu):
status: Triaged → Fix Committed
assignee: nobody → Dustin Kirkland (kirkland)
milestone: none → ubuntu-12.04-beta-2
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ssh-import-id - 2.10-0ubuntu1

---------------
ssh-import-id (2.10-0ubuntu1) precise; urgency=low

  * === added directory img, img/ssh-import-id_14.png, img/ssh-import-
    id_192.png, img/ssh-import-id_64.png, img/ssh-import-id.png:
    - add logos to revision control
  * ssh-import-id, ssh-import-id.1: LP: #944367
    - add -e parameter, which says "don't clean my environment"
    - helps if someone needs to set $https_proxy
 -- Dustin Kirkland <email address hidden> Tue, 31 Jan 2012 16:01:59 -0600

Changed in ssh-import-id (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.