diff options
author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2012-01-22 00:28:18 -0600 |
---|---|---|
committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2012-01-22 00:28:18 -0600 |
commit | 7021f40c13f949b7cb5ded32d0241d648a43bf6c (patch) | |
tree | aa1a5e4de2963edc6638783246b2ff25e98833aa /README.pam | |
parent | 0a2a54a02254ded760afd5b9c965c6bb71459d46 (diff) | |
download | tdebase-7021f40c13f949b7cb5ded32d0241d648a43bf6c.tar.gz tdebase-7021f40c13f949b7cb5ded32d0241d648a43bf6c.zip |
Part 1 of 2 of kdm rename
Diffstat (limited to 'README.pam')
-rw-r--r-- | README.pam | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/README.pam b/README.pam index 544b4e83f..c7db9908a 100644 --- a/README.pam +++ b/README.pam @@ -1,5 +1,5 @@ KDE can be configured to support the PAM ("Pluggable Authentication -Modules") system for password checking by the display manager kdm and +Modules") system for password checking by the display manager tdm and by the screen saver kscreensaver (for unlocking the display). PAM is a flexible application-transparent configurable user-authentication @@ -27,7 +27,7 @@ By default, PAM is automatically used, if it is found. Use If PAM is found, KDE usually uses the PAM service "kde". You may override it for all KDE programs by using --with-pam=<service> and/or individually by using --with-<prog>-pam=<service>, where <prog> is -one of kdm, kcp and kss (for kdm, kcheckpass and kscreensaver). +one of tdm, kcp and kss (for tdm, kcheckpass and kscreensaver). "make install" will attempt to create suitable service definitions; either by putting files into /etc/pam.d/ or by adding text to /etc/pam.conf. The @@ -35,18 +35,18 @@ services are just copies of the "login" service. You may want to edit these definitions to meet your needs. There are also two example service definitions in this directory - kde.pamd and kscreensaver.pamd - but don't just copy them! -If the services are misconfigured, you will NOT be able to login via KDM +If the services are misconfigured, you will NOT be able to login via TDM and/or unlock a locked screen! If there is ever any doubt about which PAM service a program was compiled with, it can be determined by examining the PAM-generated -entries in the system log associated with kdm logins or kscreensaver +entries in the system log associated with tdm logins or kscreensaver authentication failures. PAM configuration files have four types of entries for each service: -type used by kdm used by kscreensaver +type used by tdm used by kscreensaver ---- ----------- -------------------- auth x x account x @@ -58,10 +58,10 @@ configuration files and PAM documentation on your system for guidance as to what entries to make. If you call a PAM service that is not configured, the default action of PAM is likely to be denial of service. -Note: kdm implements PAM "session" support, which is not implemented in +Note: tdm implements PAM "session" support, which is not implemented in certain PAM-aware xdm's that it may be replacing (e.g., the Red Hat Linux 5.x xdm did not implement it). This may be configured to carry out -actions when a user opens or closes an kdm session, if a suitable PAM +actions when a user opens or closes an tdm session, if a suitable PAM module is available (e.g., mount and unmount user-specific filesystems). Note 2: Screensavers typically only authenticate a user to allow her to |