os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Whitespace cleanup from last commit.

Browse source 
No content changes.

Approved by:	murray
This commit is contained in:
Ceri Davies 2002-04-29 12:05:36 +00:00
parent c56ca257a6
commit 459ac1baba
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=12906
1 changed files with 20 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -6273,7 +6273,8 @@ C:\="DOS"</programlisting>
<qandaentry>
<question id="su-wheel-group">
<para>Why do I get the error, <errorname>you are not in the correct
group to su root</errorname> when I try to su to <username>root</username>?</para>
group to su root</errorname> when I try to su to
<username>root</username>?</para>
</question>
<answer>
@ -6736,7 +6737,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<qandaentry>
<question id="forgot-root-pw">
<para>I have forgotten the <username>root</username> password! What do I do?</para>
<para>I have forgotten the <username>root</username> password! What
do I do?</para>
</question><answer>
<para>Do not Panic! Simply restart the system, type
@ -6747,8 +6749,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<command>mount -u /</command> to remount your root filesystem
read/write, then run <command>mount -a</command> to remount all
the filesystems. Run <command>passwd root</command> to change
the <username>root</username> password then run &man.exit.1; to continue
booting.</para>
the <username>root</username> password then run &man.exit.1; to
continue booting.</para>
</answer>
</qandaentry>
@ -6975,7 +6977,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<para>Take the <literal>ntalk</literal> service, for
example (see /etc/inetd.conf). This service used to run
as userid <username>root</username>. Now it runs as userid <username>tty</username>. The <username>tty</username> user
as userid <username>root</username>. Now it runs as userid
<username>tty</username>. The <username>tty</username> user
is a sandbox designed to make it more difficult for
someone who has successfully hacked into the system via
ntalk from being able to hack beyond that user id.</para>
@ -7895,9 +7898,9 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>All X servers need to be run as <username>root</username> in order to get direct
access to your video hardware. Older versions of XFree86
(&lt;= 3.3.6) installed all bundled servers to be automatically
run as <username>root</username> (setuid to <username>root</username>). This is obviously a security
hazard because X servers are large, complicated programs.
Newer versions of XFree86 do not install the servers setuid to
run as <username>root</username> (setuid to <username>root</username>).
This is obviously a security hazard because X servers are large, complicated
programs. Newer versions of XFree86 do not install the servers setuid to
<username>root</username> for just this reason.</para>
<para>Obviously, running an X server as the <username>root</username> user is not
@ -9029,9 +9032,9 @@ Key F15 A A Menu Workplace Nop</programlisting>
you will be prompted for the path to a shell).</para>
<para>Some people use <username>toor</username> for
day-to-day <username>root</username> tasks with a non-standard shell, leaving
<username>root</username>, with a standard shell, for
single user mode or emergencies. By default you cannot log
day-to-day <username>root</username> tasks with a non-standard
shell, leaving <username>root</username>, with a standard shell,
for single user mode or emergencies. By default you cannot log
in using <username>toor</username> as it does not have a
password, so log in as <username>root</username> and set a password for
<username>toor</username> if you want to use it.</para>
@ -10447,16 +10450,17 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<filename>/etc/gettytab</filename>, see &man.gettytab.5;).
The terminal type for this port is <literal>dialup</literal>.
The port is <literal>on</literal> and is
<literal>insecure</literal>---meaning <username>root</username> logins on the port
are not allowed. For dialin ports like this one, use the
<devicename>ttyd<replaceable>X</replaceable></devicename> entry.</para>
<literal>insecure</literal>---meaning <username>root</username>
logins on the port are not allowed. For dialin ports like this one,
use the <devicename>ttyd<replaceable>X</replaceable></devicename>
entry.</para>
<para>It is common practice to use <literal>dialup</literal> as
the terminal type. Many users set up in their <filename>.profile</filename> or
<filename>.login</filename> files a prompt for the actual terminal type if the
starting type is dialup. The example shows the port as
insecure. To become <username>root</username> on this port, you have to login as a
regular user, then &man.su.1; to become
insecure. To become <username>root</username> on this port, you
have to login as a regular user, then &man.su.1; to become
<username>root</username>. If you use <literal>secure</literal>
then <username>root</username> can login in directly.</para>