From e44533f13ffb075c586d256589f8544f545566b4 Mon Sep 17 00:00:00 2001 From: Dima Dorfman Date: Fri, 16 Mar 2001 01:35:30 +0000 Subject: [PATCH] Explain the existence of the toor account. PR: 25656 Submitted by: mark drayton Approved by: nik --- en_US.ISO8859-1/books/faq/book.sgml | 37 +++++++++++++++++++++++++++- en_US.ISO_8859-1/books/faq/book.sgml | 37 +++++++++++++++++++++++++++- 2 files changed, 72 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index b56a863338..94ad8c9ecb 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -14,7 +14,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.156 2001/03/15 01:57:58 dd Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.157 2001/03/15 02:02:41 dd Exp $ 1995 @@ -6217,6 +6217,41 @@ define(`confDELIVERY_MODE',`deferred')dnl + + + What's this UID 0 toor account? Have I + been compromised? + + + + Don't worry. toor is an + alternative superuser account (toor is root + spelt backwards). Previously it was created when the + &man.bash.1; shell was installed but now it is created by + default. It is intended to be used with a non-standard shell so + you don't have to change root'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 + /usr/local/bin which, by default, resides + on a different filesystem. If root's shell + is located in /usr/local/bin and + /usr (or whatever filesystem contains + /usr/local/bin) isn't mounted for some + reason, root won't be able to log in to + fix a problem (although if you reboot into single user mode + you'll be prompted for the path to a shell). + + Some people use toor for + day-to-day root tasks with a non-standard shell, leaving + root, with a standard shell, 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 if you want to use it. + + + Eek! I forgot the root password! diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index b56a863338..94ad8c9ecb 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -14,7 +14,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.156 2001/03/15 01:57:58 dd Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.157 2001/03/15 02:02:41 dd Exp $ 1995 @@ -6217,6 +6217,41 @@ define(`confDELIVERY_MODE',`deferred')dnl + + + What's this UID 0 toor account? Have I + been compromised? + + + + Don't worry. toor is an + alternative superuser account (toor is root + spelt backwards). Previously it was created when the + &man.bash.1; shell was installed but now it is created by + default. It is intended to be used with a non-standard shell so + you don't have to change root'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 + /usr/local/bin which, by default, resides + on a different filesystem. If root's shell + is located in /usr/local/bin and + /usr (or whatever filesystem contains + /usr/local/bin) isn't mounted for some + reason, root won't be able to log in to + fix a problem (although if you reboot into single user mode + you'll be prompted for the path to a shell). + + Some people use toor for + day-to-day root tasks with a non-standard shell, leaving + root, with a standard shell, 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 if you want to use it. + + + Eek! I forgot the root password!