freebsd-skq/etc/pam.d/imap

#
# $FreeBSD$
#
# PAM configuration for the "imap" service
#

# auth
#auth		sufficient	pam_krb5.so		no_warn try_first_pass
#auth		sufficient	pam_ssh.so		no_warn try_first_pass
auth		required	pam_unix.so		no_warn try_first_pass

# account
#account	required	pam_nologin.so
account		required	pam_unix.so
pam.d-style configuration, auto-generated from pam.conf. Sponsored by: DARPA, NAI Labs 2001-12-05 21:06:21 +00:00			`#`
			`# $FreeBSD$`
			`#`
			`# PAM configuration for the "imap" service`
			`#`

			`# auth`
Major cleanup & homogenization. 2003-02-10 00:50:03 +00:00			`#auth sufficient pam_krb5.so no_warn try_first_pass`
			`#auth sufficient pam_ssh.so no_warn try_first_pass`
			`auth required pam_unix.so no_warn try_first_pass`
Now pam_nologin(8) will provide an account management function instead of an authentication function. There are a design reason and a practical reason for that. First, the module belongs in account management because it checks availability of the account and does no authentication. Second, there are existing and potential PAM consumers that skip PAM authentication for good or for bad. E.g., sshd(8) just prefers internal routines for public key auth; OTOH, cron(8) and atrun(8) do implicit authentication when running a job on behalf of its owner, so their inability to use PAM auth is fundamental, but they can benefit from PAM account management. Document this change in the manpage. Modify /etc/pam.d files accordingly, so that pam_nologin.so is listed under the "account" function class. Bump __FreeBSD_version (mostly for ports, as this change should be invisible to C code outside pam_nologin.) PR: bin/112574 Approved by: des, re 2007-06-10 18:57:20 +00:00
			`# account`
			`#account required pam_nologin.so`
Locked out and expired accounts shouldn't be accessible via remote mailbox protocols. Add pam_unix to the `account' function class, too, for imap and pop3 to actually implement this policy. 2007-06-15 11:33:13 +00:00			`account required pam_unix.so`