[bug #32501] Manual page does not include a warning for GREP_OPTIONS

[Seungbeom Kim]

Follow-up Comment #4, bug #32501 (project grep):

I've been bitten by this too. -n is another option that seems nice and
harmless on an interactive setting but that causes problems when the output is
piped into a script.

Unsetting GREP_OPTIONS cannot be the responsibility of scripts, because there
are already tons of old scripts that don't even know about GREP_OPTIONS. If
scripts were required to defend themselves even in the presence of such
environment variables, they would always have to start any serious work with
an empty environment.

Security could be an issue if the program could be allowed to execute
something not supposed to be executed, especially when the program is setuid
as root, but it's not the case here; it's not a security flaw of grep per se.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?32501>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/