|
|
|
|
@ -18,9 +18,9 @@
|
|
|
|
|
<title>The &kdm; Handbook</title>
|
|
|
|
|
|
|
|
|
|
<authorgroup>
|
|
|
|
|
<author>
|
|
|
|
|
&Oswald.Buddenhagen; &Oswald.Buddenhagen.mail;
|
|
|
|
|
</author><!--
|
|
|
|
|
<corpauthor>
|
|
|
|
|
The &kde; Documentation Team
|
|
|
|
|
</corpauthor><!--
|
|
|
|
|
<othercredit role="developer">
|
|
|
|
|
&Oswald.Buddenhagen; &Oswald.Buddenhagen.mail;
|
|
|
|
|
<contrib>Developer</contrib>
|
|
|
|
|
@ -49,16 +49,21 @@
|
|
|
|
|
<holder>&Lauri.Watts;</holder>
|
|
|
|
|
</copyright>
|
|
|
|
|
|
|
|
|
|
<date>2003-03-01</date>
|
|
|
|
|
<releaseinfo>0.05.02</releaseinfo>
|
|
|
|
|
<copyright>
|
|
|
|
|
<year>2011</year>
|
|
|
|
|
<holder>The TDE Documentation Team</holder>
|
|
|
|
|
</copyright>
|
|
|
|
|
|
|
|
|
|
<date>2011-11-01</date>
|
|
|
|
|
<releaseinfo>3.5.13</releaseinfo>
|
|
|
|
|
|
|
|
|
|
<abstract>
|
|
|
|
|
<para>This document describes &kdm; the &kde; Display Manager. &kdm;
|
|
|
|
|
<para>This document describes &kdm;, the &kde; Display Manager. &kdm;
|
|
|
|
|
is also known as the <quote>Login Manager</quote>.</para>
|
|
|
|
|
</abstract>
|
|
|
|
|
|
|
|
|
|
<keywordset>
|
|
|
|
|
<keyword>KDE</keyword>
|
|
|
|
|
<keyword>TDE</keyword>
|
|
|
|
|
<keyword>kdm</keyword>
|
|
|
|
|
<keyword>xdm</keyword>
|
|
|
|
|
<keyword>display manager</keyword>
|
|
|
|
|
@ -78,7 +83,7 @@ Display Manager, in a number of ways.</para>
|
|
|
|
|
</chapter>
|
|
|
|
|
|
|
|
|
|
<!-- Chapters to write -->
|
|
|
|
|
<!-- * Just enough config to get it to run and login to KDE
|
|
|
|
|
<!-- * Just enough config to get it to run and login to TDE
|
|
|
|
|
* Adding more session types (GNOME, etc)
|
|
|
|
|
* Adding other customizations to XSession (ssh/gpg-agent, etc)
|
|
|
|
|
* Further customization to KDM (via the kcontrol module, and by
|
|
|
|
|
@ -164,8 +169,15 @@ through the rest of this manual to find out how to do these things.</para>
|
|
|
|
|
<chapter id="login">
|
|
|
|
|
<title>The Login Window</title>
|
|
|
|
|
|
|
|
|
|
<para> The user interface to &kdm; consists of two dialog boxes. The main
|
|
|
|
|
dialog box has these controls:</para>
|
|
|
|
|
<para>The &kdm; interface consists of two dialog boxes: a login dialog
|
|
|
|
|
and a shutdown dialog.</para>
|
|
|
|
|
|
|
|
|
|
<note><para>The &kdm; interface might be protected by the Trinity Secure Access
|
|
|
|
|
Key (SAK) mechanism. When the SAK is enabled, users are prompted to press
|
|
|
|
|
<keycombo action="simul">&Ctrl; &Alt;<keycap>Delete</keycap></keycombo>
|
|
|
|
|
to obtain access to the &kdm; interface.</para></note>
|
|
|
|
|
|
|
|
|
|
<para>The main login dialog box has these controls:</para>
|
|
|
|
|
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
@ -296,16 +308,16 @@ main &kdm; dialog box. </para>
|
|
|
|
|
<para>This chapter assumes that &kdm; is already up and running on your
|
|
|
|
|
system, and that you simply want to change its behavior in some way.</para>
|
|
|
|
|
|
|
|
|
|
<para>When &kdm; starts up, it reads its configuration from the folder
|
|
|
|
|
<para>Upon starting, &kdm; reads its configuration from the folder
|
|
|
|
|
<filename class="directory">$KDEDIR/share/config/kdm/</filename> (this may
|
|
|
|
|
be <filename class="directory">/etc/trinity/kdm/</filename> or something else
|
|
|
|
|
on your system).</para>
|
|
|
|
|
|
|
|
|
|
<para>The main configuration file is &kdmrc;; all other files are
|
|
|
|
|
referenced from there and could be stored under any name anywhere on
|
|
|
|
|
the system - but usually that would not make much sense for obvious
|
|
|
|
|
the system. Usually that would not make much sense for obvious
|
|
|
|
|
reasons (one particular exception is referencing configuration files
|
|
|
|
|
of an already installed &xdm; - however when a new &kdm; is installed,
|
|
|
|
|
of an already installed &xdm;. However, when a new &kdm; is installed,
|
|
|
|
|
it will import settings from those files if it finds an already installed
|
|
|
|
|
&xdm;).</para>
|
|
|
|
|
|
|
|
|
|
@ -313,26 +325,24 @@ it will import settings from those files if it finds an already installed
|
|
|
|
|
associated with any particular user. Therefore, it is not possible to have
|
|
|
|
|
user-specific configuration files; all users share the common &kdmrc;. It
|
|
|
|
|
follows from this that the configuration of &kdm; can only be altered by
|
|
|
|
|
those users that have write access to
|
|
|
|
|
those users who have write access to
|
|
|
|
|
<filename>$<envar>KDEDIR</envar>/share/config/kdm/kdmrc</filename> (normally
|
|
|
|
|
restricted to system administrators logged in as <systemitem
|
|
|
|
|
class="username">root</systemitem>).</para>
|
|
|
|
|
|
|
|
|
|
<para>You can view the &kdmrc; file currently in use on your system, and you
|
|
|
|
|
can configure &kdm; by editing this file. Alternatively, you can use the
|
|
|
|
|
can configure &kdm; by editing that file. Alternately, you can use the
|
|
|
|
|
graphical configuration tool provided by the &kcontrolcenter; (under
|
|
|
|
|
<menuchoice><guisubmenu>System Administration</guisubmenu><guimenuitem>Login
|
|
|
|
|
Manager</guimenuitem></menuchoice>), which is described in <ulink
|
|
|
|
|
url="help:/kcontrol/login-manager.html">the &kcontrolcenter; help files</ulink>.
|
|
|
|
|
Manager</guimenuitem></menuchoice>), which is described in the next section.
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>The remainder of this chapter describes configuration of &kdm;
|
|
|
|
|
via the &kcontrolcenter; module, and the <link linkend="kdm-files">next
|
|
|
|
|
<para>The remainder of this chapter describes configuring &kdm;
|
|
|
|
|
using the &kcontrolcenter; module, and the <link linkend="kdm-files">next
|
|
|
|
|
chapter</link> describes the options available in &kdmrc; itself. If
|
|
|
|
|
you only need to configure for local users, the &kcontrolcenter; module
|
|
|
|
|
should be sufficient for your needs. If you need to configure remote
|
|
|
|
|
logins, or have multiple &kdm; sessions running, you will need to read
|
|
|
|
|
on.</para>
|
|
|
|
|
logins, or have multiple &kdm; sessions running, you will need to continue reading.</para>
|
|
|
|
|
|
|
|
|
|
<sect1 id="kdm-kcontrol-module">
|
|
|
|
|
<sect1info>
|
|
|
|
|
@ -353,7 +363,8 @@ computer.</para>
|
|
|
|
|
<note><para>All settings will be written to the configuration file
|
|
|
|
|
&kdmrc;, which in its original state has many comments to help you
|
|
|
|
|
configure &kdm;. Using this &kcontrolcenter; module will strip these
|
|
|
|
|
comments from the file. All available options in &kdmrc; are covered
|
|
|
|
|
comments from the file. Consider making a backup of &kdmrc; before
|
|
|
|
|
making changes. All available options in &kdmrc; are covered
|
|
|
|
|
in <xref linkend="kdm-files"/>.</para>
|
|
|
|
|
|
|
|
|
|
<para>The options listed in this chapter are cross referenced with
|
|
|
|
|
@ -376,7 +387,7 @@ linkend="kdmconfig-convenience"><guilabel>Convenience</guilabel></link>.</para>
|
|
|
|
|
the window.</para>
|
|
|
|
|
|
|
|
|
|
<note><para>If you are not currently logged in as a superuser, you
|
|
|
|
|
will need to click the <guibutton>Administrator Mode...</guibutton>
|
|
|
|
|
will need to select the <guibutton>Administrator Mode...</guibutton>
|
|
|
|
|
Button. You will then be asked for a superuser password. Entering a
|
|
|
|
|
correct password will allow you to modify the settings of this
|
|
|
|
|
module.</para></note>
|
|
|
|
|
@ -439,6 +450,49 @@ linkend="option-colorscheme"><option>ColorScheme</option></link> in
|
|
|
|
|
your login box, corresponding to setting <option>Language</option> in
|
|
|
|
|
&kdmrc;.</para>
|
|
|
|
|
|
|
|
|
|
<para>In this same section &kdm; can be configured to use a <guilabel>Secure
|
|
|
|
|
Attention Key</guilabel> (SAK). A Secure Attention Key is a special key press
|
|
|
|
|
to which only certain privileged applications are able to respond, such as the
|
|
|
|
|
login and screen unlock dialogs. This mechanism prevents a malevolent user
|
|
|
|
|
from creating an exact copy of the login screen to "sniff" or "phish" passwords
|
|
|
|
|
or other sensitive information. The unprivileged copy is unable to detect the
|
|
|
|
|
SAK key press, thereby providing a visible difference in operation to the
|
|
|
|
|
user.</para>
|
|
|
|
|
|
|
|
|
|
<para>When the Trinity SAK is enabled, users are prompted to press
|
|
|
|
|
<keycombo action="simul">&Ctrl; &Alt;<keycap>Delete</keycap></keycombo>
|
|
|
|
|
before sensitive information is requested.
|
|
|
|
|
|
|
|
|
|
<screenshot>
|
|
|
|
|
<screeninfo>The Trinity Secure Attention Key dialog</screeninfo>
|
|
|
|
|
<mediaobject>
|
|
|
|
|
<imageobject>
|
|
|
|
|
<imagedata fileref="tsak.png" format="PNG"/>
|
|
|
|
|
</imageobject>
|
|
|
|
|
<textobject><phrase>The Trinity Secure Attention Key dialog</phrase>
|
|
|
|
|
</textobject>
|
|
|
|
|
</mediaobject>
|
|
|
|
|
</screenshot>
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>When SAK is enabled, and the
|
|
|
|
|
<keycombo action="simul">&Ctrl; &Alt;<keycap>Delete</keycap></keycombo>
|
|
|
|
|
dialog does not appear before sensitive information is requested, someone might
|
|
|
|
|
be attempting to "phish" for that information. A prudent course of action would
|
|
|
|
|
be to terminate the active X11 session via <keycombo action="simul">&Ctrl; &Alt;
|
|
|
|
|
<keycap>Backspace</keycap></keycombo> or any other distribution-specific key press
|
|
|
|
|
for this action, thereby restoring control to the kernel and base system.</para>
|
|
|
|
|
|
|
|
|
|
<para>Generally, using the Trinity SAK is a good idea when supporting many
|
|
|
|
|
graphical login accounts on a machine. For example, in enterprise environments
|
|
|
|
|
or computer laboratories. When only one graphical login account is used, or
|
|
|
|
|
only a few accounts in a controlled environment, such as with a home computer,
|
|
|
|
|
Trinity SAK will not provide tangible benefits over the standard login
|
|
|
|
|
methods.</para>
|
|
|
|
|
|
|
|
|
|
<note><para>Trinity SAK requires evdev to be running and the Linux uinput kernel
|
|
|
|
|
module to be loaded.</para></note>
|
|
|
|
|
|
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
|
|
<sect2 id="kdmconfig-font">
|
|
|
|
|
@ -1079,8 +1133,8 @@ addressing and security; the sockets all have the file name
|
|
|
|
|
<literal>rw-rw-rw-</literal> (0666). This is because some systems don't care
|
|
|
|
|
for the file permission of the socket files.</para>
|
|
|
|
|
|
|
|
|
|
<para>There are two types of sockets: the global one (dmctl) and the
|
|
|
|
|
per-display ones (dmctl-<display>).</para>
|
|
|
|
|
<para>There are two types of sockets: the global one (kdmctl) and the
|
|
|
|
|
per-display ones (kdmctl-<display>).</para>
|
|
|
|
|
|
|
|
|
|
<para>The global one's subdir is owned by root, the subdirs of the per-display
|
|
|
|
|
ones' are owned by the user currently owning the session (root or the
|
|
|
|
|
|
Darrell Anderson
