trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] Bug 1902 - pam.d and preprocessor checks surrounding consolekit may be part of issue

From: François Andriot <francois.andriot@...>
Date: Tue, 25 Feb 2014 07:03:04 +0100
Le 25/02/2014 05:43, David C. Rankin a �crit :
> On 02/24/2014 10:34 PM, David C. Rankin wrote:
>> showing that session tracking can with
> Grrr... autotext, should be:
>
> showing that session tracking can work in TDE...
>

Here are the PAM files I'm using on Mageia 4.
This is simply a copy/paste from what KDE4 uses on the same distribution.

I've done some investigation on this issue and I'll write my findings 
later (not enough time right now).

Francois
#%PAM-1.0
auth       include	system-auth
account    include	system-auth
password   include	system-auth
session    include	system-auth
#%PAM-1.0
auth       required    pam_env.so
auth       required    pam_succeed_if.so 
auth       sufficient  pam_succeed_if.so user ingroup nopasswdlogin
auth       substack    system-auth
account    required    pam_nologin.so
account    include     system-auth
password   include     system-auth
session    required    pam_loginuid.so
session    optional    pam_console.so
session    optional    pam_keyinit.so force revoke
session    required    pam_namespace.so
session    include     system-auth
#%PAM-1.0
auth       required    pam_env.so
auth       required    pam_permit.so
account    required    pam_nologin.so
account    include     system-auth
password   include     system-auth
session    required    pam_loginuid.so
session    optional    pam_console.so
session    optional    pam_keyinit.so force revoke
session    required    pam_namespace.so
session    include     system-auth
#%PAM-1.0
auth       include	system-auth
account    include	system-auth
password   include	system-auth
session    include	system-auth