komputes: They aren't in the init scripts, etc.

The problem is that if a user adds GREP_OPTIONS to their environment
(manually, or via .bashrc, etc.) then it can break init.d scripts, etc.

At the time, if you did `env GREP_OPTIONS=-E /etc/init.d/blah start` it
could break the `blah` script in unpredictable ways.  Also it can break
various scripts in /usr/bin and /bin

Depending on the users setup, GREP_OPTIONS may also make it through a
sudo call.

The reason why this is a problem is that troubleshooting this kind of
problem can be very difficult because only the person with GREP_OPTIONS
set will have the breakage and it'll not be obvious that this is
happening.

I hope that clears this up.

Ciao!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/67141

Title:
  Please create and enforce a system-wide policy to unset GREP_OPTION by
  default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/67141/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to