Bug#523882: sudo -i doesn't unset some environment variables

2021-02-24 Thread Marc Haber
Hi, this is one of the monster bugs of sudo that has seen a lot of discussion years ago. On Mon, Apr 13, 2009 at 12:43:18PM +0200, Vincent Lefevre wrote: > The sudo man page says: > > -i The -i (simulate initial login) option runs the shell specified in > the passwd(5) entry of the

Bug#523882: sudo -i doesn't unset some environment variables

2012-01-26 Thread Vincent Lefevre
On 2012-01-26 06:33:56 +0100, Jan Braun wrote: Ha, I think I got it. LS_COLORS is included by default in env_keep. If you don't set (or just append to) env_keep, LS_COLORS will be passed on, irrespective of -i and/or env_reset. If you overwrite env_keep (by assigning to it), LS_COLORS will be

Bug#523882: sudo -i doesn't unset some environment variables

2012-01-25 Thread Vincent Lefevre
found 523882 1.8.3p1-3 thanks On 2012-01-25 09:44:22 +0100, Jan Braun wrote: fixed 392321 1.8.3p1-2 fixed 523882 1.8.3p1-2 thanks Hi, both these bugs have been fixed in the meantime. I doubt that 523882 has been fixed. It is still present in the latest sudo version. The man pages have

Bug#523882: sudo -i doesn't unset some environment variables

2012-01-25 Thread Vincent Lefevre
found 523882 1.8.3p1-2 thanks On 2012-01-25 10:25:15 +0100, Vincent Lefevre wrote: On 2012-01-25 09:44:22 +0100, Jan Braun wrote: fixed 392321 1.8.3p1-2 fixed 523882 1.8.3p1-2 thanks Hi, both these bugs have been fixed in the meantime. I doubt that 523882 has been fixed. It is

Bug#523882: sudo -i doesn't unset some environment variables

2012-01-25 Thread Jan Braun
Vincent Lefevre schrob: However, though my /etc/environment is an empty file, some other variables are preserved. This includes LC_* variables, LS_COLORS, COLORTERM and XAUTHORITY. Example: # export LS_COLORS=blah # sudo -i env | grep LS_ LS_COLORS=blah Works for me: | # LS_COLORS=blah

Bug#523882: sudo -i doesn't unset some environment variables

2012-01-25 Thread Vincent Lefevre
On 2012-01-26 00:50:22 +0100, Jan Braun wrote: I wondered whether pam could have an influence, but I haven't seen LS_COLORS listed in related files. Might be. My /etc/sudoers contains Defaults env_reset Same for me. and no mention of LS_COLORS. xvii:/# grep -r LS_COLORS /etc /root

Bug#523882: sudo -i doesn't unset some environment variables

2012-01-25 Thread Jan Braun
And I get the same problem on another machine. That's strange. Ha, I think I got it. LS_COLORS is included by default in env_keep. If you don't set (or just append to) env_keep, LS_COLORS will be passed on, irrespective of -i and/or env_reset. If you overwrite env_keep (by assigning to it),

Bug#523882: sudo -i doesn't unset some environment variables

2009-04-13 Thread Vincent Lefevre
Package: sudo Version: 1.6.9p17-2 Severity: normal The sudo man page says: -i The -i (simulate initial login) option runs the shell specified in the passwd(5) entry of the user that the command is being run as. The command name argument given to the shell begins with a `-' to

Bug#523882: sudo -i doesn't unset some environment variables

2009-04-13 Thread Bdale Garbee
On Mon, 2009-04-13 at 12:43 +0200, Vincent Lefevre wrote: Package: sudo Version: 1.6.9p17-2 This code has changed significantly for version 1.7.0-1, now in unstable. The man page for option -i now reads: -i [command] The -i (simulate initial login) option runs the shell

Bug#523882: sudo -i doesn't unset some environment variables

2009-04-13 Thread Vincent Lefevre
On 2009-04-13 13:27:40 -0600, Bdale Garbee wrote: If you could try 1.7.0-1, I would be interested to know if the behavior you see matches expectations set by the man page. It not, then I will certainly pursue this further. I have sudo 1.7.0-1 on another machine (Debian/unstable), and there's

Bug#523882: sudo -i doesn't unset some environment variables

2009-04-13 Thread Bdale Garbee
On Tue, 2009-04-14 at 00:22 +0200, Vincent Lefevre wrote: On 2009-04-13 13:27:40 -0600, Bdale Garbee wrote: If you could try 1.7.0-1, I would be interested to know if the behavior you see matches expectations set by the man page. It not, then I will certainly pursue this further. I have