If ubuntu-system-services is setting the proxy information in apt's
config already, I don't think there's actually anything more to be done
here. We should definitely *not* be whitelisting the http_proxy variable
for sudo, as this allows a user with restricted sudo access to mitm
attack http traffi
To be clear ubuntu-system-services sets the proxy server for you in
/etc/apt/apt.conf:
root@flash:/etc/apt# cat apt.conf
APT::Authentication::TrustCDROM "true";
Acquire::http::proxy "http://192.68.10.1:3128/";;
Acquire::https::proxy "https://192.68.10.1:3128/";;
Acquire::ftp::proxy "ftp://192.68.1
Given Martin's comment in #29, and the -E or /etc/sudoers solutions, is
there really anything to do in apt? I don't think you want apt to get
the proxy from ubuntu-system-services (although maybe it makes sense to
do so optionally if the service can be contacted).
--
You received this bug notifi
Note that for many releases now the proxy configuration guy (through
ubuntu-system-service) is supposed to set the proxy in both the
environment and the apt configuration. It will also ask you whether you
want to apply a proxy configuration system-wide if you try to change it
for your user only. Is
** Changed in: apt (Ubuntu)
Milestone: None => ubuntu-12.04
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Tags added: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/556293
Title:
apt/aptitude need to take global proxy settings into account
To manage notifications about this bug go to:
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/556293
Title:
apt/aptitude need to take global proxy settings into account
To manage notifications about this bug go
Taylor - I know that is a valid solution for many situations but it is
not really a workaround, that is using the wrong users environment
settings.
I have been working for 3 years with the Amazon Cloud from inside a big
corporate and I am sick to the back teeth of these proxy issues that
have been
There is a simpler workaround to preserve the http_proxy environment
variable:
sudo -E apt-get install ...
However this preserves all other (potentially dangerous) environment
variables. The point is that that environment variables which are safe
and commonly needed in a sudo environment should b
Just as an update to this issue, it exists as of today on Ubuntu Natty
64bits. As noted above, the following circumvent it.
1) sudo sh
2) apt-get install ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I also agree with Mike. I'm constrained to specific proxies here at
work.
My pain point being 'sudo wget' during 'make' scripts.
(Used workarounds from comment #16 successfully)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
I agree with Mike. I assume sudo takes the whitelist approach to
environment variables for security purposes (versus passing everything
through and only blacklisting some), but that means the the default
whitelist should be actively maintained so that that the most common use
case scenarios work ou
I can tell you that as a user of Ubuntu systems behind firewalls (where
the only way to get out is an HTTP proxy), I would *always* want
http_proxy to be passed through. Otherwise, if I want to run something
that connects via http to the Internet, I have to do:
$ sudo -i
Password:
# export http_pr
I strongly disagree with that idea. Reading from /etc/environment means
that user-specific proxy settings are lost.
Not letting apt receive the environment properly from its parent also
means that you can't set up a temporary environment where all web
fetches ought to go through a proxy, when you
sudo is the wrong place to fix this, I'm afraid. What should happen
instead is that apt itself should use the global proxy settings, either
directly from /etc/environment, or indirectly by changing ubuntu-system-
service to additionally write an apt configuration file with the proxy
settings. Micha
15 matches
Mail list logo
