From mark@type49.com  Sat Mar 10 08:07:15 2001
Return-Path: <mark@type49.com>
Received: from type49.com (type49.com [195.26.32.125])
	by hub.freebsd.org (Postfix) with ESMTP id B8EE137B718
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 10 Mar 2001 08:07:14 -0800 (PST)
	(envelope-from mark@type49.com)
Received: by type49.com (Postfix, from userid 1001)
	id 0C89D1AD2; Sat, 10 Mar 2001 16:07:07 +0000 (GMT)
Message-Id: <20010310160707.0C89D1AD2@type49.com>
Date: Sat, 10 Mar 2001 16:07:07 +0000 (GMT)
From: mark@type49.com
Reply-To: mark@type49.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: New FAQ entry for 'toor' account (PATCH)
X-Send-Pr-Version: 3.2

>Number:         25656
>Category:       docs
>Synopsis:       New FAQ entry for 'toor' account (PATCH)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Mar 10 08:10:01 PST 2001
>Closed-Date:    Thu Mar 15 17:37:12 PST 2001
>Last-Modified:  Thu Mar 15 17:38:42 PST 2001
>Originator:     mark drayton
>Release:        FreeBSD 4.2-STABLE i386
>Organization:
>Environment:

FreeBSD type49.com 4.2-STABLE FreeBSD 4.2-STABLE #0: Tue Feb 13 13:43:54 GMT 2001     root@type49.com:/usr/obj/usr/src/sys/GENERIC  i386

>Description:

New FAQ entry to answer "what's this 'toor' account?"

>How-To-Repeat:

Read -questions.

>Fix:

*** /usr/doc/en_US.ISO_8859-1/books/faq/book.sgml       Thu Mar  8 11:01:25 2001
--- book.sgml   Sat Mar 10 15:35:17 2001
***************
*** 6263,6268 ****
--- 6263,6297 ----
        </qandaentry>

        <qandaentry>
+         <question id="toor-account">
+           <para>What's this UID 0 'toor' account? Have I been compromised?</para>
+         </question>
+
+         <answer>
+           <para>Don't worry. toor is an 'alternative' root account
+             (toor is root spelt backwards). Previously it was created
+             when the bash shell was installed but recently it has been
+             created by default. It was installed with bash so you
+             could use the bash shell as a root user, without changing
+             the real root user's default shell. This is important as
+             bash would likely be installed in <filename>/usr/local/bin
+             </filename> which, by default, resides on a different disk
+             partition. If root's shell is set to <filename>
+             /usr/local/bin/bash</filename> and <filename>/usr</filename>
+             is unmountable for some reason, root won't be able to log in
+             to fix the problem (although if you reboot into single user
+             mode you'll be prompted for the path to a shell).</para>
+           <para>
+             Some people use toor for day-to-day root tasks with the bash
+             shell, leaving root (with /bin/csh or /bin/sh) for single
+             user mode or emergencies. By default you can't log in using
+             toor as it doesn't have a password, so log in as root and
+             set a password for toor: <screen>&prompt.root; <userinput>passwd toor</userinput></screen>
+             then log out and try logging in as toor.</para>
+         </answer>
+       </qandaentry>
+
+       <qandaentry>
          <question id="forgot-root-pw">
            <para>Eek! I forgot the root password!</para>
          </question><answer>

>Release-Note:
>Audit-Trail:

From: Dima Dorfman <dima@unixfreak.org>
To: mark@type49.com
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: docs/25656: New FAQ entry for 'toor' account (PATCH) 
Date: Mon, 12 Mar 2001 19:53:00 -0800

 mark@type49.com writes:
 > 
 > >Number:         25656
 > >Category:       docs
 > >Synopsis:       New FAQ entry for 'toor' account (PATCH)
 > >Description:
 > 
 > New FAQ entry to answer "what's this 'toor' account?"
 
 A few suggestions:
 
   - This seems to imply that bash is the only shell that can be used
     with toor; this isn't true.
   - Please try to follow the existing style in the file (newlines
     after </para>; <screen> goes outside of <para>).
   - 'toor' and 'root' should probably be surrounded with <username> tags.
 
 Other than that, it looks pretty good.
 
 Thanks
 
 					Dima Dorfman
 					dima@unixfreak.org

From: mark@type49.com (mark drayton)
To: dima@unixfreak.org
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: docs/25656: New FAQ entry for 'toor' account (PATCH)
Date: Wed, 14 Mar 2001 10:46:06 +0000 (GMT)

 diffed against doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.154
 
 --- /usr/doc/en_US.ISO_8859-1/books/faq/book.sgml	Wed Mar 14 06:40:16 2001
 +++ book.sgml	Wed Mar 14 10:26:09 2001
 @@ -6303,6 +6303,40 @@
        </qandaentry>
  
        <qandaentry>
 +        <question id="toor-account">
 +          <para>What's this UID 0 'toor' account? Have I been compromised?</para>
 +        </question>
 +
 +        <answer>
 +          <para>Don't worry. <username>toor</username> is an 'alternative'
 +            superuser account (toor is root spelt backwards). Previously
 +            it was created when the &man.bash.1; shell was installed but
 +            recently it has been created by default. It is intended to
 +            be used with a non-standard shell so you don't have to
 +            change <username>root</username>'s default shell. This is
 +            important as shells which aren't part of the base
 +            distribution (for example a shell installed from ports or
 +            packages) are likely be to be installed in
 +            <filename>/usr/local/bin</filename> which, by default,
 +            resides on a different disk partition. If <username>root</username>'s
 +            shell is located in <filename> /usr/local/bin</filename>
 +            and <filename>/usr</filename> (or whatever partition
 +            contains <filename>/usr/local/bin</filename>) is unmountable
 +            for some reason, <username>root</username> won't be able to
 +            log in to fix the problem (although if you reboot into
 +            single user mode you'll be prompted for the path to a shell).</para>          <para>Some people use <username>toor</username> for day-to-day
 +            root tasks with a non-standard shell, leaving <username>root</username>
 +            (with <filename>/bin/csh</filename> or <filename>/bin/sh</filename>)            for single user mode or emergencies. By default you can't
 +            log in using <username>toor</username> as it doesn't have a
 +            password, so log in as root and set a password for
 +            <username>toor</username>:</para>
 +            <screen>&prompt.root; <userinput>passwd toor</userinput></screen>
 +
 +          <para>then log out and try logging in as <username>toor</username>.</para>
 +        </answer>
 +      </qandaentry>
 +
 +      <qandaentry>
          <question id="forgot-root-pw">
            <para>Eek! I forgot the root password!</para>
          </question><answer>
State-Changed-From-To: open->closed 
State-Changed-By: dd 
State-Changed-When: Thu Mar 15 17:37:12 PST 2001 
State-Changed-Why:  
Committed, thanks! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=25656 
>Unformatted:
