| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
not allocate a pty(4) so it is not suitable at all for interactive
PAM modules. rlogind calls login(1) which is already PAM enabled.
Approved by: markm
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
S/Key authentication for ftpd was not working due to ftp implementation and
/etc/pam.conf missmatch.
So add ftpd entries into /etc/pam.conf.
Reported by: "Jose M. Alcaide" <jose@we.lc.ehu.es>
Approved by: jkh
Reviewed by: markm
|
|
|
|
|
| |
PR: conf/14714
Submitted by: Ronald F. Guilmette <rfg@monkeys.com>
|
|
|
|
| |
folk over various hurdles.
|
| |
|
|
|
|
| |
Reviewed by: markm (in concept)
|
|
methods used by login. Changes to "/usr/bin/login" to use it will
be committed later today. The format of the file is described in
pam(8).
This sample file makes login behave in the traditional way. To
wit, it enables authentication via S/Key and passwd/NIS lookups.
KerberosIV authentication is present in the sample file but commented
out.
As a safety net and a transition aid, login will fall back on
built-in passwd/NIS authentication if this configuration file is
missing or if some other fatal PAM error occurs.
This file will eventually replace "/etc/auth.conf", but not until
I've finished converting the other utilities, such as passwd and su.
|