registry team mailing list archive

[Bill Mills <wmills@xxxxxx>]

More info & a workaround for sudo

Operation of wget has not changed.  wget will fail in 9.04 just the same
as 10.04  if trailing comma is added to no_proxy.  Wrong no_proxy value
appears to be added by gnome-terminal (at least) as it starts.  If you
run xterm direct from a launcher no special handling of the gnome proxy
settings is done. (Which in this case is a good thing.)  Best workaround
for this is to sed the no_proxy in .bashrc as was suggested elsewhere.

sudo defaults have changed between 9.04 and 10.04.  In 9.04 http_proxy
(but not no_proxy) was included in the default env_keep list. (You can
see built in defaults with "sudo sudo -V" ).  Since no_proxy was not
included it was not really correct in 9.04 either (but I never noticed).
I verified that a "sudo wget localurl" fails in 9.04.  (Its not that
that paragraph did not have enough not's in it. NOT!)

The fix/workaround for either version is to explicitly configure the env
vars you want to pass through sudo.

sudo visudo

Find the existing line that starts with the word "Defaults", below that add this line:
Defaults        env_keep+="http_proxy no_proxy"

Warning: only use visudo and don't save the file if it says you have an
error, it will lock you out of sudo and you will need to use the
recovery console. (Yes I know from experience, but not this time.)

-- 
wget does not use network proxy in some cases
https://bugs.launchpad.net/bugs/232469
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.