From: Todd C. Miller <Todd.Miller@courtesan.com>
Date: Tue, 5 Apr 2011 13:18:13 +0000 (-0400)
Subject: Merge SETENV and NOSETENV description from 1.8
X-Git-Tag: SUDO_1_7_6~4
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=440d255bf770e5da182cdeb8dedeb6d91b46d90b;p=sudo

Merge SETENV and NOSETENV description from 1.8

--HG--
branch : 1.7
---

diff --git a/sudoers.pod b/sudoers.pod
index d93cd60d7..ef250cd7c 100644
--- a/sudoers.pod
+++ b/sudoers.pod
@@ -443,13 +443,14 @@ on how C<NOEXEC> works and whether or not it will work on your system.
 =head3 SETENV and NOSETENV
 
 These tags override the value of the I<setenv> option on a per-command
-basis.  Note that if C<SETENV> has been set for a command, any
-environment variables set on the command line way are not subject
-to the restrictions imposed by I<env_check>, I<env_delete>, or
-I<env_keep>.  As such, only trusted users should be allowed to set
-variables in this manner.  If the command matched is B<ALL>, the
-C<SETENV> tag is implied for that command; this default may
-be overridden by use of the C<NOSETENV> tag.
+basis.  Note that if C<SETENV> has been set for a command, the user
+may disable the I<env_reset> option from the command line via the
+B<-E> option.  Additionally, environment variables set on the command
+line are not subject to the restrictions imposed by I<env_check>,
+I<env_delete>, or I<env_keep>.  As such, only trusted users should
+be allowed to set variables in this manner.  If the command matched
+is B<ALL>, the C<SETENV> tag is implied for that command; this
+default may be overridden by use of the C<NOSETENV> tag.
 
 =head3 LOG_INPUT and NOLOG_INPUT