freebsd-dev/etc/pam.d/Makefile

# $FreeBSD$

.include <src.opts.mk>

NO_OBJ=

FILES=	README \
	cron \
	ftpd \
	imap \
	login \
	other \
	passwd pop3 \
	rsh \
	sshd su system \
	telnetd \
	xdm

.if ${MK_AT} != "no"
FILES+=	atrun
.endif

FILESDIR=	/etc/pam.d
FILESMODE=	644
FILESMODE_README=	444
LINKS=	${FILESDIR}/ftpd ${FILESDIR}/ftp

.include <bsd.prog.mk>
Makefile for pam.d configuration files. Sponsored by: DARPA, NAI Labs 2001-12-06 13:16:47 +00:00			`# $FreeBSD$`

Honor MK_ACCT with etc/pam.d/atrun MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division 2015-01-26 08:50:12 +00:00			`.include <src.opts.mk>`

Start the dreaded NOFOO -> NO_FOO conversion. OK'ed by: core 2004-12-21 08:47:35 +00:00			`NO_OBJ=`
Split the FILES list across multiple lines as in rc.d/Makefile so that the change history stays easily readable as the number of PAM-aware services grows. 2007-06-15 11:22:10 +00:00
			`FILES= README \`
Add PAM support to cron(8). Now cron(8) will skip commands scheduled by unavailable accounts, e.g., those locked, expired, not allowed in at the moment by nologin(5), or whatever, depending on cron's pam.conf(5). This applies to personal crontabs only, /etc/crontab is unaffected. In other words, now the account management policy will apply to commands scheduled by users via crontab(1) so that a user can no longer use cron(8) to set up a delayed backdoor and run commands during periods when the admin doesn't want him to. The PAM check is done just before running a command, not when loading a crontab, because accounts can get locked, expired, and re-enabled any time with no changes to their crontabs. E.g., imagine that you provide a system with payed access, or better a cluster of such systems with centralized account management via PAM. When a user pays for some days of access, you set his expire field respectively. If the account expires before its owner pays more, its crontab commands won't run until the next payment is made. Then it'll be enough to set the expire field in future for the commands to run again. And so on. Document this change in the cron(8) manpage, which includes adding a FILES section and touching the document date. X-Security: should benefit as users have access to cron(8) by default 2007-06-17 17:25:53 +00:00			`cron \`
Split the FILES list across multiple lines as in rc.d/Makefile so that the change history stays easily readable as the number of PAM-aware services grows. 2007-06-15 11:22:10 +00:00			`ftpd \`
			`imap \`
			`login \`
			`other \`
			`passwd pop3 \`
			`rsh \`
			`sshd su system \`
			`telnetd \`
			`xdm`

Honor MK_ACCT with etc/pam.d/atrun MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division 2015-01-26 08:50:12 +00:00			`.if ${MK_AT} != "no"`
			`FILES+= atrun`
			`.endif`

Fixed bugs in previous revision: Added NOOBJ if anyone even attempts to "make obj" here. Revert to installing files with mode 644 except README. Make this overall look like a BSD-style Makefile rather than roll-your-own (this is not a bug). For the record. Previous revision also fixed the breakage introduced by the sys.mk,v 1.60 commit: bsd.own.mk is no longer automatically included from sys.mk. Reported by: jhay 2002-04-18 10:58:14 +00:00			`FILESDIR= /etc/pam.d`
			`FILESMODE= 644`
			`FILESMODE_README= 444`
Use the canonical form of installing links. Also, make "ftp" and "ftpd" hard links. Not objected to by: des 2003-03-14 09:01:22 +00:00			`LINKS= ${FILESDIR}/ftpd ${FILESDIR}/ftp`
There's no reason to have two identical policies for FTP servers, so make ftp a symlink to ftpd. 2003-02-10 00:47:46 +00:00
Use ${FILES} and <bsd.prog.mk> rather than roll-your-own. 2002-04-18 10:07:36 +00:00			`.include <bsd.prog.mk>`