freebsd-skq/etc/pam.d/other

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

# auth
auth		sufficient	pam_opie.so		no_warn no_fake_prompts
auth		requisite	pam_opieaccess.so	no_warn allow_local
#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_krb5.so
account		required	pam_login_access.so
account		required	pam_unix.so

# session
#session	optional	pam_ssh.so		want_agent
session		required	pam_permit.so

# password
password	required	pam_permit.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 "other" service`
			`#`

			`# auth`
Major cleanup & homogenization. 2003-02-10 00:50:03 +00:00			`auth sufficient pam_opie.so no_warn no_fake_prompts`
Add the allow_local option to all pam_opieaccess entries. 2003-02-16 13:02:39 +00:00			`auth requisite pam_opieaccess.so no_warn allow_local`
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`
pam.d-style configuration, auto-generated from pam.conf. Sponsored by: DARPA, NAI Labs 2001-12-05 21:06:21 +00:00
			`# account`
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 required pam_nologin.so`
tabify MFC after: 3 weeks 2009-10-05 09:28:54 +00:00			`#account required pam_krb5.so`
Major cleanup & homogenization. 2003-02-10 00:50:03 +00:00			`account required pam_login_access.so`
Awright, egg on my face. I should have taken more time with this. The conversion script generated the wrong format, so the configuration files didn't actually work. Good thing I hadn't thrown the switch yet... Sponsored by: DARPA, NAI Labs (but the f***ups are all mine) 2001-12-05 21:26:00 +00:00			`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
			`# session`
tabify MFC after: 3 weeks 2009-10-05 09:28:54 +00:00			`#session optional pam_ssh.so want_agent`
Major cleanup & homogenization. 2003-02-10 00:50:03 +00:00			`session required pam_permit.so`
pam.d-style configuration, auto-generated from pam.conf. Sponsored by: DARPA, NAI Labs 2001-12-05 21:06:21 +00:00
			`# password`
Major cleanup & homogenization. 2003-02-10 00:50:03 +00:00			`password required pam_permit.so`