From owner-freebsd-doc@FreeBSD.ORG Fri Dec 9 13:20:07 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC081106564A for ; Fri, 9 Dec 2011 13:20:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B7CA38FC19 for ; Fri, 9 Dec 2011 13:20:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pB9DK7Xc029442 for ; Fri, 9 Dec 2011 13:20:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pB9DK7QI029433; Fri, 9 Dec 2011 13:20:07 GMT (envelope-from gnats) Resent-Date: Fri, 9 Dec 2011 13:20:07 GMT Resent-Message-Id: <201112091320.pB9DK7QI029433@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Chris Whitehouse Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D0971065670 for ; Fri, 9 Dec 2011 13:10:17 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 6BC288FC14 for ; Fri, 9 Dec 2011 13:10:17 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id pB9DAGUp056829 for ; Fri, 9 Dec 2011 13:10:17 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id pB9DAGJx056828; Fri, 9 Dec 2011 13:10:16 GMT (envelope-from nobody) Message-Id: <201112091310.pB9DAGJx056828@red.freebsd.org> Date: Fri, 9 Dec 2011 13:10:16 GMT From: Chris Whitehouse To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/163149: [patch] Red Hat Linux/i386 9 HTML format man page is mangled X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2011 13:20:07 -0000 >Number: 163149 >Category: docs >Synopsis: [patch] Red Hat Linux/i386 9 HTML format man page is mangled >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 09 13:20:06 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Chris Whitehouse >Release: 8.1R >Organization: n/a >Environment: FreeBSD muji2.config 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:55:53 UTC 2010 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: http://www.freebsd.org/cgi/man.cgi?query=sudo&apropos=0&sektion=0&manpath=Red+Hat+Linux%2Fi386+9&arch=default&format=html shows S ssuuddoo --VV | --hh | --ll | --LL | --vv | --kk | --KK | --ss | [ --HH ] [--PP ] [--SS ] [ --bb ] | [ --pp prompt ] [ --cc class|- ] [ --aa auth_type ] [ --uu username|#uid ] command and more similar stuff >How-To-Repeat: Just view http://www.freebsd.org/cgi/man.cgi?query=sudo&apropos=0&sektion=0&manpath=Red+Hat+Linux%2Fi386+9&arch=default&format=html in a browser. >Fix: Attached is a diff of the page as saved from my browser (Firefox 3-6-10) to my machine and the corrected page. This might not be a useful way of doing it as it is probably dynamically generated, in which case let me know of a better way and I'll have another go. (Some of the other Red Hat man pages have the same problem, once I have a working method of correcting them I will do them as well) Patch attached with submission follows: --- sudo_redhat_i386_9.cgi 2011-12-08 22:00:17.000000000 +0000 +++ sudo_redhat_i386_9_new.cgi 2011-12-08 22:50:48.000000000 +0000 @@ -451,133 +451,133 @@ 
 sudo(8) 		     MAINTENANCE COMMANDS		       sudo(8)
 
-N
+NAME
        sudo - execute a command as another user
 
-S
-       ssuuddoo --VV | --hh | --ll | --LL | --vv | --kk | --KK | --ss | [ --HH ] [--PP ] [--SS ] [ --bb ]
-       | [ --pp prompt ] [ --cc class|- ] [ --aa auth_type ] [ --uu username|#uid ]
+SYNOPSIS
+       sudo -V | -h | -l | -L | -v | -k | -K | -s | [ -H ] [-P ] [-S ] [ -b ]
+       | [ -p prompt ] [ -c class|- ] [ -a auth_type ] [ -u username|#uid ]
        command
 
-D
-       ssuuddoo allows a permitted user to execute a command as the superuser or
+DESCRIPTION
+       sudo allows a permitted user to execute a 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).  By default, ssuuddoo requires that users authenticate
+       user is not root).  By default, sudo requires that users authenticate
        themselves with a password (NOTE: by default this is the user's pass-
        word, 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 (5 minutes unless overridden in sudoers).
 
-       ssuuddoo determines who is an authorized user by consulting the file
-       /etc/sudoers.  By giving ssuuddoo the --vv flag a user can update the time
+       sudo determines who is an authorized user by consulting the file
+       /etc/sudoers.  By giving sudo the --vv flag a user can update the time
        stamp without running a command. The password prompt itself will also
        time out if the user's password is not entered within 5 minutes (unless
        overridden via sudoers).
 
        If a user who is not listed in the sudoers file tries to run a command
-       via ssuuddoo, mail is sent to the proper authorities, as defined at config-
+       via sudo, mail is sent to the proper authorities, as defined at config-
        ure time or the sudoers file (defaults to root).  Note that the mail
        will not be sent if an unauthorized user tries to run sudo with the --ll
        or --vv flags.  This allows users to determine for themselves whether or
-       not they are allowed to use ssuuddoo.
+       not they are allowed to use sudo.
 
-       ssuuddoo can log both successful and unsuccessful attempts (as well as
-       errors) to syslog(3), a log file, or both.  By default ssuuddoo will log
+       sudo can log both successful and unsuccessful attempts (as well as
+       errors) to syslog(3), a log file, or both.  By default sudo will log
        via syslog(3) but this is changeable at configure time or via the sudo-
        ers file.
 
-O
-       ssuuddoo accepts the following command line options:
+OPTIONS
+       sudo accepts the following command line options:
 
-       -V  The --VV (version) option causes ssuuddoo to print the version number and
-	   exit.  If the invoking user is already root the --VV option will
-	   print out a list of the defaults ssuuddoo was compiled with as well as
+       -V  The -V (version) option causes sudo to print the version number and
+	   exit.  If the invoking user is already root the -V option will
+	   print out a list of the defaults sudo was compiled with as well as
 	   the machine's local network addresses.
 
-       -l  The --ll (list) option will list out the allowed (and forbidden) com-
+       -l  The -l (list) option will list out the allowed (and forbidden) com-
 	   mands for the user on the current host.
 
-       -L  The --LL (list defaults) option will list out the parameters that may
+       -L  The -L (list defaults) option will list out the parameters that may
 	   be set in a Defaults line along with a short description for each.
 	   This option is useful in conjunction with grep(1).
 
-       -h  The --hh (help) option causes ssuuddoo to print a usage message and exit.
+       -h  The -h (help) option causes sudo to print a usage message and exit.
 
-       -v  If given the --vv (validate) option, ssuuddoo will update the user's
+       -v  If given the -v (validate) option, sudo will update the user's
 	   timestamp, prompting for the user's password if necessary.  This
-	   extends the ssuuddoo timeout for another 5 minutes (or whatever the
+	   extends the sudo timeout for another 5 minutes (or whatever the
 	   timeout is set to in sudoers) but does not run a command.
 
-       -k  The --kk (kill) option to ssuuddoo invalidates the user's timestamp by
-	   setting the time on it to the epoch.  The next time ssuuddoo is run a
+       -k  The -k (kill) option to sudo invalidates the user's timestamp by
+	   setting the time on it to the epoch.  The next time sudo is run a
 	   password will be required.  This option does not require a password
-	   and was added to allow a user to revoke ssuuddoo permissions from a
+	   and was added to allow a user to revoke sudo permissions from a
 	   .logout file.
 
-       -K  The --KK (sure kill) option to ssuuddoo removes the user's timestamp
+       -K  The -K (sure kill) option to sudo removes the user's timestamp
 	   entirely.  Likewise, this option does not require a password.
 
-       -b  The --bb (background) option tells ssuuddoo to run the given command in
-	   the background.  Note that if you use the --bb option you cannot use
+       -b  The -b (background) option tells sudo to run the given command in
+	   the background.  Note that if you use the -b option you cannot use
 	   shell job control to manipulate the process.
 
-       -p  The --pp (prompt) option allows you to override the default password
+       -p  The -p (prompt) option allows you to override the default password
 	   prompt and use a custom one.  If the password prompt contains the
 	   %u escape, %u will be replaced with the user's login name.  Simi-
 	   larly, %h will be replaced with the local hostname.
 
-       -c  The --cc (class) option causes ssuuddoo to run the specified command with
+       -c  The -c (class) option causes sudo to run the specified command with
 	   resources limited by the specified login class.  The class argument
 	   can be either a class name as defined in /etc/login.conf, or a sin-
 	   gle '-' character.  Specifying a class of - indicates that the com-
 	   mand should be run restricted by the default login capabilities for
 	   the user the command is run as.  If the class argument specifies an
-	   existing user class, the command must be run as root, or the ssuuddoo
+	   existing user class, the command must be run as root, or the sudo
 	   command must be run from a shell that is already root.  This option
-	   is only available on systems with BSD login classes where ssuuddoo has
+	   is only available on systems with BSD login classes where sudo has
 	   been configured with the --with-logincap option.
 
-       -a  The --aa (authentication type) option causes ssuuddoo to use the speci-
+       -a  The -a (authentication type) option causes sudo to use the speci-
 	   fied authentication type when validating the user, as allowed by
 	   /etc/login.conf.  The system administrator may specify a list of
 	   sudo-specific authentication methods by adding an "auth-sudo" entry
 	   in /etc/login.conf.	This option is only available on systems that
-	   support BSD authentication where ssuuddoo has been configured with the
+	   support BSD authentication where sudo has been configured with the
 	   --with-bsdauth option.
 
-       -u  The --uu (user) option causes ssuuddoo to run the specified command as a
+       -u  The -u (user) option causes sudo to run the specified command as a
 	   user other than root.  To specify a uid instead of a username, use
 	   #uid.
 
-       -s  The --ss (shell) option runs the shell specified by the SHELL envi-
+       -s  The -s (shell) option runs the shell specified by the SHELL envi-
 	   ronment variable if it is set or the shell as specified in
 	   passwd(5).
 
-       -H  The --HH (HOME) option sets the HOME environment variable to the
+       -H  The -H (HOME) option sets the HOME environment variable to the
 	   homedir of the target user (root by default) as specified in
-	   passwd(5).  By default, ssuuddoo does not modify HOME.
+	   passwd(5).  By default, sudo does not modify HOME.
 
-       -P  The --PP (preserve group vector) option causes ssuuddoo to preserve the
-	   user's group vector unaltered.  By default, ssuuddoo will initialize
+       -P  The -P (preserve group vector) option causes sudo to preserve the
+	   user's group vector unaltered.  By default, sudo will initialize
 	   the group vector to the list of groups the target user is in.  The
 	   real and effective group IDs, however, are still set to match the
 	   target user.
 
-       -S  The --SS (stdin) option causes ssuuddoo to read the password from stan-
+       -S  The -S (stdin) option causes sudo to read the password from stan-
 	   dard input instead of the terminal device.
 
-       --  The ---- flag indicates that ssuuddoo should stop processing command line
-	   arguments.  It is most useful in conjunction with the --ss flag.
+       --  The -- flag indicates that sudo should stop processing command line
+	   arguments.  It is most useful in conjunction with the -s flag.
 
-R
-       Upon successful execution of a program, the return value from ssuuddoo will
+RETURN VALUES
+       Upon successful execution of a program, the return value from sudo will
        simply be the return value of the program that was executed.
 
-       Otherwise, ssuuddoo quits with an exit value of 1 if there is a configura-
-       tion/permission problem or if ssuuddoo cannot execute the given command.
-       In the latter case the error string is printed to stderr.  If ssuuddoo can-
+       Otherwise, sudo quits with an exit value of 1 if there is a configura-
+       tion/permission problem or if sudo cannot execute the given command.
+       In the latter case the error string is printed to stderr.  If sudo can-
        not stat(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
@@ -586,40 +586,40 @@
        mounter and one of the directories in your PATH is on a machine that is
        currently unreachable.
 
-S
-       ssuuddoo tries to be safe when executing external commands.	Variables that
+SECURITY NOTES
+       sudo tries to be safe when executing external commands.	Variables that
        control how dynamic loading and binding is done can be used to subvert
-       the program that ssuuddoo runs.  To combat this the LD_*, _RLD_*,
+       the program that sudo runs.  To combat this the LD_*, _RLD_*,
        SHLIB_PATH (HP-UX only), and LIBPATH (AIX only) environment variables
        are removed from the environment passed on to all commands executed.
-       ssuuddoo will also remove the IFS, ENV, BASH_ENV, KRB_CONF, KRBCONFDIR,
+       sudo will also remove the IFS, ENV, BASH_ENV, KRB_CONF, KRBCONFDIR,
        KRBTKFILE, KRB5_CONFIG, LOCALDOMAIN, RES_OPTIONS, HOSTALIASES, NLSPATH,
        PATH_LOCALE, TERMINFO, TERMINFO_DIRS and TERMPATH variables as they too
        can pose a threat.  If the TERMCAP variable is set and is a pathname,
        it too is ignored.  Additionally, if the LC_* or LANGUAGE variables
-       contain the / or % characters, they are ignored.  If ssuuddoo has been com-
+       contain the / or % characters, they are ignored.  If sudo has been com-
        piled with SecurID support, the VAR_ACE, USR_ACE and DLC_ACE variables
-       are cleared as well.  The list of environment variables that ssuuddoo
+       are cleared as well.  The list of environment variables that sudo
        clears is contained in the output of sudo -V when run as root.
 
-       To prevent command spoofing, ssuuddoo checks "." and "" (both denoting cur-
+       To prevent command spoofing, sudo checks "." and "" (both denoting cur-
        rent directory) last when searching for a command in the user's PATH
        (if one or both are in the PATH).  Note, however, that the actual PATH
        environment variable is not modified and is passed unchanged to the
-       program that ssuuddoo executes.
+       program that sudo executes.
 
        For security reasons, if your OS supports shared libraries and does not
        disable user-defined library search paths for setuid programs (most
        do), you should either use a linker option that disables this behavior
-       or link ssuuddoo statically.
+       or link sudo statically.
 
-       ssuuddoo will check the ownership of its timestamp directory (/var/run/sudo
+       sudo will check the ownership of its timestamp directory (/var/run/sudo
        by default) and ignore the directory's contents if it is not owned by
        root and only writable by root.	On systems that allow non-root users
        to give away files via chown(2), if the timestamp directory is located
        in a directory writable by anyone (e.g.: /tmp), it is possible for a
-       user to create the timestamp directory before ssuuddoo is run.  However,
-       because ssuuddoo checks the ownership and mode of the directory and its
+       user to create the timestamp directory before sudo is run.  However,
+       because sudo checks the ownership and mode of the directory and its
        contents, the only damage that can be done is to "hide" files by
        putting them in the timestamp dir.  This is unlikely to happen since
        once the timestamp dir is owned by root and inaccessible by any other
@@ -629,21 +629,21 @@
        /var/run/sudo with the appropriate owner (root) and permissions (0700)
        in the system startup files.
 
-       ssuuddoo will not honor timestamps set far in the future.  Timestamps with
+       sudo 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 systems that allow users to
        give away files.
 
-       Please note that ssuuddoo will only log the command it explicitly runs.  If
+       Please note that sudo will only log the command it explicitly runs.  If
        a user runs a command such as sudo su or sudo sh, subsequent commands
-       run from that shell will not be logged, nor will ssuuddoo's access control
+       run from that shell will not be logged, nor will sudo's access control
        affect them.  The same is true for commands that offer shell escapes
        (including most editors).  Because of this, care must be taken when
-       giving users access to commands via ssuuddoo to verify that the command
+       giving users access to commands via sudo to verify that the command
        does not inadvertantly give the user an effective root shell.
 
-E
+EXAMPLES
        Note: the following examples assume suitable sudoers(5) entries.
 
        To get a file listing of an unreadable directory:
@@ -669,8 +669,8 @@
 
 	% sudo sh -c "cd /home ; du -s * | sort -rn > USAGE"
 
-E
-       ssuuddoo utilizes the following environment variables:
+ENVIRONMENT
+       sudo 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
@@ -686,31 +686,31 @@
 	SUDO_GID	       Set to the gid of the user who invoked sudo
 	SUDO_PS1	       If set, PS1 will be set to its value
 
-F
+FILES
 	/etc/sudoers	       List of who can run what
 	/var/run/sudo		   Directory containing timestamps
 
-A
-       Many people have worked on ssuuddoo over the years; this version consists
+AUTHORS
+       Many people have worked on sudo over the years; this version consists
        of code written primarily by:
 
 	       Todd Miller
 	       Chris Jepeway
 
-       See the HISTORY file in the ssuuddoo distribution or visit
-       http://www.sudo.ws/sudo/history.html for a short history of ssuuddoo.
+       See the HISTORY file in the sudo distribution or visit
+       http://www.sudo.ws/sudo/history.html for a short history of sudo.
 
-B
+BUGS
        If you feel you have found a bug in sudo, please submit a bug report at
        http://www.sudo.ws/sudo/bugs/
 
-D
-       SSuuddoo is provided ``AS IS'' and any express or implied warranties,
+DISCLAIMER
+       Sudo is provided ``AS IS'' and any express or implied warranties,
        including, but not limited to, the implied warranties of merchantabil-
        ity and fitness for a particular purpose are disclaimed.  See the
-       LICENSE file distributed with ssuuddoo for complete details.
+       LICENSE file distributed with sudo for complete details.
 
-C
+CAVEATS
        There is no easy way to prevent a user from gaining a root shell if
        that user has access to commands allowing shell escapes.
 
@@ -718,12 +718,12 @@
        their own program that gives them a root shell regardless of any '!'
        elements in the user specification.
 
-       Running shell scripts via ssuuddoo can expose the same kernel bugs that
+       Running shell scripts via sudo 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).
 
-S
+SEE_ALSO
        stat(2), login_cap(3), sudoers(5), passwd(5), visudo(8), grep(1),
        su(1).
 
@@ -731,20 +731,21 @@
-N | -S | -D | -O | -R | -S | -E | -E | -F | -A | -B | -D | -C | -S +NAME | +SYNOPSIS | +DESCRIPTION | +OPTIONS | +RETURN VALUES | +SECURITY NOTES | +ENVIRONMENT | +FILES | +EXAMPLES | +SEE ALSO | +AUTHORS | +CAVEATS | +BUGS | +SUPPORT | +DISCLAIMER

Want to link to this manual page? Use this URL:
<http://www.freebsd.org/cgi/man.cgi?query=sudo&manpath=Red+Hat+Linux%2fi386+9>

home | help
>Release-Note: >Audit-Trail: >Unformatted: