Bug 25656

Summary: New FAQ entry for 'toor' account (PATCH)
Product: Documentation Reporter: mark <mark>
Component: Books & ArticlesAssignee: freebsd-doc (Nobody) <doc>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description mark 2001-03-10 16:10:01 UTC
New FAQ entry to answer "what's this 'toor' account?"

Fix: 

<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>--iYPgVHH2UxPva5L7aWQ0Z10M3zY2PsDVYlRGwnCLJVOyHxIf
Content-Type: text/plain; name="file.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="file.diff"

*** /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>
How-To-Repeat: 
Read -questions.
Comment 1 dima 2001-03-13 03:53:00 UTC
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
Comment 2 mark 2001-03-14 10:46:06 UTC
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>
Comment 3 dd freebsd_committer freebsd_triage 2001-03-16 01:37:12 UTC
State Changed
From-To: open->closed

Committed, thanks!