freebsd-dev/etc/pam.d/pop3

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

# auth
#auth		required	pam_nologin.so	no_warn
#auth		sufficient	pam_opie.so	no_warn no_fake_prompts
#auth		requisite	pam_opieaccess.so	no_warn
#auth		required	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			`#`
			`# $FreeBSD$`
			`#`
			`# PAM configuration for the "pop3" service`
			`#`

			`# auth`
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			`#auth required pam_nologin.so no_warn`
Enable OPIE by default, using the no_fake_prompts option to hide it from users who don't wish to use it. If the admin is worried about leaking information about which users exist and which have OPIE enabled, the no_fake_prompts option can simply be removed. Also insert the appropriate pam_opieaccess lines after pam_opie to break the chain in case the user is logging in from an untrusted host, or has a .opiealways file. The entire opieaccess / opiealways concept is slightly unpammish, but admins familiar with OPIE will expect it to work. Reviewed by: ache, markm Sponsored by: DARPA, NAI Labs 2002-01-21 18:51:24 +00:00			`#auth sufficient pam_opie.so no_warn no_fake_prompts`
			`#auth requisite pam_opieaccess.so no_warn`
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			`#auth required pam_ssh.so no_warn try_first_pass`
			`#auth required pam_unix.so no_warn try_first_pass`