Whatever.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/207768
Title:
no_proxy environment dropped when calling synaptic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
Passing these variables by default potentially allows a user to MITM the
network connections of a process running as a different user and feed it
untrusted input. This is not something that should be implemented in
sudo.
** Changed in: sudo (Ubuntu)
Status: Confirmed => Won't Fix
--
You
should add https_proxy as well.
Affected with this bug as Apport crash reporter makes use of sudo and
communicate via HTTPS.
When a system program crash, it can not report due to non-exported https_proxy
and unavailable HTTPS here without dialing the proxy.
--
You received this bug notificatio
I don't know whether I want to see my wget using libproxy.
Anyway, I added the line mentioned in comment #4 to my /etc/sudoers (note, that
putting that into /etc/sudoers.d/keepenv didn't work because #includedir
/etc/sudoers.d is missing).
Now it works as pre-lucid, i.e. I can update my system u
On Fri, 2009-11-20 at 14:08 +, Hubert FONGARNAND wrote:
> >Or as an even better workaround, heck, no, solution,
> update-manager/synaptic could just use libproxy and not have to worry
> about parsing all those variables itself.
>
>
> Don't do that please... dpkg can call other tools like (wg
>Or as an even better workaround, heck, no, solution,
update-manager/synaptic could just use libproxy and not have to worry
about parsing all those variables itself.
Don't do that please... dpkg can call other tools like (wget) :> example when
you install the flash player...
And all these tool d
On Fri, 2009-11-20 at 13:39 +, Troy Astle wrote:
> As a work around for those effected by this bug you can tell sudo to
> pass through the no_proxy environment variable by adding the following
> line to /etc/sudoers
Or as an even better workaround, heck, no, solution,
update-manager/synaptic
** Tags added: sudo
--
no_proxy environment dropped when calling synaptic
https://bugs.launchpad.net/bugs/207768
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
As a work around for those effected by this bug you can tell sudo to
pass through the no_proxy environment variable by adding the following
line to /etc/sudoers
Defaultsenv_keep="no_proxy http_proxy XAUTHORIZATION XAUTHORITY
TZ PS2 PS1 PATH MAIL LS_COLORS KRB5CCNAME HOSTNAME HOME DISPLAY C
I'm using my own mirror in our firm... but it's unsuable because some
app needs http_proxy variable... and there's no way to tell apt not use
http_proxy variable...
Our last hope was no_proxy variable... it works well with apt which
understant this useful variable... but not with sudo!
So having
We'll probably have to patch env.c to include no_proxy in
initial_keepenv_table.
I'll see if I can cook up a patch.
--
no_proxy environment dropped when calling synaptic
https://bugs.launchpad.net/bugs/207768
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Thanks for your bugreport.
The latest sudo does drops most environment variable for security
reasons. I reassign this to sudo.
** Changed in: sudo (Ubuntu)
Sourcepackagename: update-manager => sudo
Status: New => Confirmed
--
no_proxy environment dropped when calling synaptic
https://bug
12 matches
Mail list logo
