diff options
Diffstat (limited to 'doc/userguide/kde-as-root.docbook')
| -rw-r--r-- | doc/userguide/kde-as-root.docbook | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/userguide/kde-as-root.docbook b/doc/userguide/kde-as-root.docbook index c97f2e5f5..510828c4e 100644 --- a/doc/userguide/kde-as-root.docbook +++ b/doc/userguide/kde-as-root.docbook @@ -9,13 +9,13 @@ </sect1info> -<title>Using &kde; as Root</title> +<title>Using &tde; as Root</title> <para>For &UNIX; operating systems there are often different users, which in turn might have different privileges. The conventional method is to have an ordinary user account, whose files are generally stored in <filename>/home/username</filename>, and then to also have a <systemitem class="username">root</systemitem> account. The <systemitem class="username">root</systemitem>, or Super User, account has system-wide privileges, being able to modify any file on the system. </para> <para>Although this means that it is easy to perform administrative tasks without hassle, it also means that there are no security restrictions imposed upon it. Thus, a small typographical error or other mistake can result in irrevocable damage.</para> -<para>Some of the operating systems that run &kde; come with a graphical <systemitem class="username">root</systemitem> login enabled. Despite this, you should never log in to &kde; as <systemitem class="username">root</systemitem>, and you should never need to. Your system is far more open to attack, particularly if you are browsing the Internet as <systemitem class="username">root</systemitem>, and you dramatically increase your chances of damaging your system.</para> +<para>Some of the operating systems that run &tde; come with a graphical <systemitem class="username">root</systemitem> login enabled. Despite this, you should never log in to &tde; as <systemitem class="username">root</systemitem>, and you should never need to. Your system is far more open to attack, particularly if you are browsing the Internet as <systemitem class="username">root</systemitem>, and you dramatically increase your chances of damaging your system.</para> <para>Some &Linux; distributions have tried to stress this point so much that they have disabled the <systemitem class="username">root</systemitem> account altogether, and instead use the <command>sudo</command> model. Nevertheless, the basic security model in <command>sudo</command> is the same as <command>su</command>, and thus they share the same security strengths and weaknesses, essentially.</para> |