On Mon, 2014-01-13 at 08:42 -0500, Matthew Miller wrote:
> On Mon, Jan 13, 2014 at 08:37:57AM -0500, Stephen Gallagher wrote:
> > that's included into other PAM stacks that require authentication. By
> > default, this is prepared by authconfig, but there are situations
> > where an admin would like
On Po, 2014-01-13 at 08:37 -0500, Stephen Gallagher wrote:
> On 01/12/2014 08:17 AM, Miroslav Suchy wrote:
> > I just wonder why `authconfig` creates: /etc/pam.d/system-auth ->
> > system-auth-ac /etc/pam.d/postlogin -> postlogin-ac
> > /etc/pam.d/password-auth -> password-auth-ac etc.
> >
> > Wh
On Mon, Jan 13, 2014 at 08:37:57AM -0500, Stephen Gallagher wrote:
> that's included into other PAM stacks that require authentication. By
> default, this is prepared by authconfig, but there are situations
> where an admin would like to take control (and not risk that later
> passes of authconfig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/12/2014 08:17 AM, Miroslav Suchy wrote:
> I just wonder why `authconfig` creates: /etc/pam.d/system-auth ->
> system-auth-ac /etc/pam.d/postlogin -> postlogin-ac
> /etc/pam.d/password-auth -> password-auth-ac etc.
>
> Why those links and why -a
I just wonder why `authconfig` creates:
/etc/pam.d/system-auth -> system-auth-ac
/etc/pam.d/postlogin -> postlogin-ac
/etc/pam.d/password-auth -> password-auth-ac
etc.
Why those links and why -ac suffix? Why it does not modify original
files directly?
Is there some story behind?
Mirek
