Be very clear that the password required is the user's not root's

diff --git a/sudo.cat b/sudo.cat
index a73a3999552d970b2b4d6fd2950cce146ebc6e76..5fc057bbf28fbc348cd26e83a66250770e26ed48 100644 (file)
--- a/sudo.cat
+++ b/sudo.cat
@@ -17,7 +17,12 @@ D\bD\bD\bDE\bE\bE\bES\bS\bS\bSC\bC\bC\bCR\bR\bR\bRI\bI\bI\bIP\bP\bP\bPT\bT\bT\bTI\bI\bI\bIO\bO\bO\bON\bN\bN\bN
        file.  The real and effective uid and gid are set to match
        those of the target user as specified in the passwd file
        (the group vector is also initialized when the target user
-       is not root).
+       is not root).  By default, s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo requires that users
+       authenticate themselves with a password (NOTE: this is the
+       user's password, not the root password).  Once a user has
+       been authenticated, a timestamp is updated and the user
+       may then use sudo without a password for a short period of
+       time (five minutes by default).
 
        s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo determines who is an authorized user by consulting
        the file _\b/_\be_\bt_\bc_\b/_\bs_\bu_\bd_\bo_\be_\br_\bs.  By giving s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo the -v flag a user
@@ -53,15 +58,10 @@ O\bO\bO\bOP\bP\bP\bPT\bT\bT\bTI\bI\bI\bIO\bO\bO\bON\bN\bN\bNS\bS\bS\bS
            with a short description for each.  This option is
            useful in conjunction with _\bg_\br_\be_\bp(1).
 
-       -h  The -h (_\bh_\be_\bl_\bp) option causes s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo to print a usage
-           message and exit.
 
-       -v  If given the -v (_\bv_\ba_\bl_\bi_\bd_\ba_\bt_\be) option, s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo will update
-           the user's timestamp, prompting for the user's
 
 
-
-15/Nov/1999                    1.6                              1
+22/Nov/1999                    1.6                              1
 
 
 
@@ -70,6 +70,11 @@ O\bO\bO\bOP\bP\bP\bPT\bT\bT\bTI\bI\bI\bIO\bO\bO\bON\bN\bN\bNS\bS\bS\bS
 sudo(8)                MAINTENANCE COMMANDS               sudo(8)
 
 
+       -h  The -h (_\bh_\be_\bl_\bp) option causes s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo to print a usage
+           message and exit.
+
+       -v  If given the -v (_\bv_\ba_\bl_\bi_\bd_\ba_\bt_\be) option, s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo will update
+           the user's timestamp, prompting for the user's
            password if necessary.  This extends the s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo timeout
            to for another N minutes (where N is defined at
            installation time and defaults to 5 minutes) but does
@@ -119,15 +124,10 @@ R\bR\bR\bRE\bE\bE\bET\bT\bT\bTU\bU\bU\bUR\bR\bR\bRN\bN\bN\bN V\bV\bV\bVA\bA\bA\bAL\bL\bL\bLU\bU\bU\bUE\bE\bE\bES\b
        configuration/permission problem or if s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo cannot execute
        the given command.  In the latter case the error string is
        printed to stderr.  If s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo cannot _\bs_\bt_\ba_\bt(2) one or more
-       entries in the user's PATH an error is printed on stderr.
-       (If the directory does not exist or if it is not really a
-       directory, the entry is ignored and no error is printed.)
-       This should not happen under normal circumstances.  The
-       most common reason for _\bs_\bt_\ba_\bt(2) to return "permission
 
 
 
-15/Nov/1999                    1.6                              2
+22/Nov/1999                    1.6                              2
 
 
 
@@ -136,6 +136,11 @@ R\bR\bR\bRE\bE\bE\bET\bT\bT\bTU\bU\bU\bUR\bR\bR\bRN\bN\bN\bN V\bV\bV\bVA\bA\bA\bAL\bL\bL\bLU\bU\bU\bUE\bE\bE\bES\b
 sudo(8)                MAINTENANCE COMMANDS               sudo(8)
 
 
+       entries in the user's PATH an error is printed on stderr.
+       (If the directory does not exist or if it is not really a
+       directory, the entry is ignored and no error is printed.)
+       This should not happen under normal circumstances.  The
+       most common reason for _\bs_\bt_\ba_\bt(2) to return "permission
        denied" is if you are running an automounter and one of
        the directories in your PATH is on a machine that is
        currently unreachable.
@@ -185,15 +190,10 @@ S\bS\bS\bSE\bE\bE\bEC\bC\bC\bCU\bU\bU\bUR\bR\bR\bRI\bI\bI\bIT\bT\bT\bTY\bY\bY\bY N\bN\bN\bNO\bO\bO\bOT\bT\bT\bTE\b
 
        s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo will not honor timestamps set far in the future.
        Timestamps with a date greater than current_time + 2 *
-       TIMEOUT will be ignored and sudo will log and complain.
-       This is done to keep a user from creating his/her own
-       timestamp with a bogus date on system that allow users to
-       give away files.
 
 
 
-
-15/Nov/1999                    1.6                              3
+22/Nov/1999                    1.6                              3
 
 
 
@@ -202,6 +202,11 @@ S\bS\bS\bSE\bE\bE\bEC\bC\bC\bCU\bU\bU\bUR\bR\bR\bRI\bI\bI\bIT\bT\bT\bTY\bY\bY\bY N\bN\bN\bNO\bO\bO\bOT\bT\bT\bTE\b
 sudo(8)                MAINTENANCE COMMANDS               sudo(8)
 
 
+       TIMEOUT will be ignored and sudo will log and complain.
+       This is done to keep a user from creating his/her own
+       timestamp with a bogus date on system that allow users to
+       give away files.
+
 E\bE\bE\bEX\bX\bX\bXA\bA\bA\bAM\bM\bM\bMP\bP\bP\bPL\bL\bL\bLE\bE\bE\bES\bS\bS\bS
        Note: the following examples assume suitable _\bs_\bu_\bd_\bo_\be_\br_\bs(5)
        entries.
@@ -250,23 +255,23 @@ E\bE\bE\bEN\bN\bN\bNV\bV\bV\bVI\bI\bI\bIR\bR\bR\bRO\bO\bO\bON\bN\bN\bNM\bM\bM\bME\bE\bE\bEN\bN\bN\bNT\bT\bT\bT
 
 
 F\bF\bF\bFI\bI\bI\bIL\bL\bL\bLE\bE\bE\bES\bS\bS\bS
-        /etc/sudoers           List of who can run what
-        /var/run/sudo          Directory containing timestamps
 
-       s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo utilizes the following environment variables:
 
 
 
+22/Nov/1999                    1.6                              4
 
 
-15/Nov/1999                    1.6                              4
 
 
 
+sudo(8)                MAINTENANCE COMMANDS               sudo(8)
 
 
-sudo(8)                MAINTENANCE COMMANDS               sudo(8)
+        /etc/sudoers           List of who can run what
+        /var/run/sudo          Directory containing timestamps
 
+       s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo utilizes the following environment variables:
 
         PATH                   Set to a sane value if SECURE_PATH is set
         SHELL                  Used to determine shell to run with -s option
@@ -317,15 +322,10 @@ C\bC\bC\bCA\bA\bA\bAV\bV\bV\bVE\bE\bE\bEA\bA\bA\bAT\bT\bT\bTS\bS\bS\bS
 
        If users have sudo ALL there is nothing to prevent them
        from creating their own program that gives them a root
-       shell regardless of any '!'  elements in the user
-       specification.
 
-       Running shell scripts via s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo can expose the same kernel
-       bugs that make setuid shell scripts unsafe on some
 
 
-
-15/Nov/1999                    1.6                              5
+22/Nov/1999                    1.6                              5
 
 
 
@@ -334,6 +334,11 @@ C\bC\bC\bCA\bA\bA\bAV\bV\bV\bVE\bE\bE\bEA\bA\bA\bAT\bT\bT\bTS\bS\bS\bS
 sudo(8)                MAINTENANCE COMMANDS               sudo(8)
 
 
+       shell regardless of any '!'  elements in the user
+       specification.
+
+       Running shell scripts via s\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo can expose the same kernel
+       bugs that make setuid shell scripts unsafe on some
        operating systems (if your OS supports the /dev/fd/
        directory, setuid shell scripts are generally safe).
 
@@ -386,11 +391,6 @@ S\bS\bS\bSE\bE\bE\bEE\bE\bE\bE A\bA\bA\bAL\bL\bL\bLS\bS\bS\bSO\bO\bO\bO
 
 
 
-
-
-
-
-
-15/Nov/1999                    1.6                              6
+22/Nov/1999                    1.6                              6
 
 

diff --git a/sudo.html b/sudo.html
index 2a3fbb2b30d9e1f4949cbe536be3dfd42be44028..ed9168b471cda7de0c2af4a52f591068db129539 100644 (file)
--- a/sudo.html
+++ b/sudo.html
@@ -50,7 +50,11 @@ sudo - execute a command as another user
 <STRONG>sudo</STRONG> allows a permitted user to execute a <EM>command</EM> as the superuser or another user, as specified in the sudoers file. The
 real and effective uid and gid are set to match those of the target user as
 specified in the passwd file (the group vector is also initialized when the
-target user is not root).
+target user is not root). By default, <STRONG>sudo</STRONG>
+requires that users authenticate themselves with a password (NOTE: this is
+the user's password, not the root password). Once a user has been
+authenticated, a timestamp is updated and the user may then use sudo
+without a password for a short period of time (five minutes by default).
 
 <P>
 <STRONG>sudo</STRONG> determines who is an authorized user by consulting the file <EM>/etc/sudoers</EM>. By giving <STRONG>sudo</STRONG> the <CODE>-v</CODE> flag a user can update the time stamp without running a <EM>command.</EM>

diff --git a/sudo.man b/sudo.man
index b597428845be03ba4e88b18d7a9b9cee43164cbe..6d9b29c82849d051d4cfda72ef96acd73260e83d 100644 (file)
--- a/sudo.man
+++ b/sudo.man
@@ -2,8 +2,8 @@
 ''' $RCSfile$$Revision$$Date$
 '''
 ''' $Log$
-''' Revision 1.39  1999/11/16 05:42:28  millert
-''' get rid of references to sudo-bugs.  Now mention the web site or the sudo@ alias
+''' Revision 1.40  1999/11/23 05:43:16  millert
+''' Be very clear that the password required is the user's not root's
 '''
 '''
 .de Sh
@@ -96,7 +96,7 @@
 .nr % 0
 .rr F
 .\}
-.TH sudo 8 "1.6" "15/Nov/1999" "MAINTENANCE COMMANDS"
+.TH sudo 8 "1.6" "22/Nov/1999" "MAINTENANCE COMMANDS"
 .UC
 .if n .hy 0
 .if n .na
@@ -200,7 +200,12 @@ sudo \- execute a command as another user
 superuser or another user, as specified in the sudoers file.  The
 real and effective uid and gid are set to match those of the target
 user as specified in the passwd file (the group vector is also
-initialized when the target user is not root).
+initialized when the target user is not root).  By default, \fBsudo\fR
+requires that users authenticate themselves with a password
+(NOTE: this is the user's password, not the root password).  Once
+a user has been authenticated, a timestamp is updated and the
+user may then use sudo without a password for a short period of time
+(five minutes by default).
 .PP
 \fBsudo\fR determines who is an authorized user by consulting the
 file \fI/etc/sudoers\fR.  By giving \fBsudo\fR the \f(CW-v\fR flag a user

diff --git a/sudo.pod b/sudo.pod
index bac988c5b79fc957cea2a0a29d053717041493cf..51f5098626fd8d8b3ed592feb823ad502ba3bcbe 100644 (file)
--- a/sudo.pod
+++ b/sudo.pod
@@ -50,7 +50,12 @@ B<sudo> allows a permitted user to execute a I<command> as the
 superuser or another user, as specified in the sudoers file.  The
 real and effective uid and gid are set to match those of the target
 user as specified in the passwd file (the group vector is also
-initialized when the target user is not root).
+initialized when the target user is not root).  By default, B<sudo>
+requires that users authenticate themselves with a password
+(NOTE: this is the user's password, not the root password).  Once
+a user has been authenticated, a timestamp is updated and the
+user may then use sudo without a password for a short period of time
+(five minutes by default).
 
 B<sudo> determines who is an authorized user by consulting the
 file F</etc/sudoers>.  By giving B<sudo> the C<-v> flag a user