summaryrefslogtreecommitdiffstats
path: root/etc/pam.d/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* Create a rcmds package.gjb2016-01-211-1/+8
| | | | Sponsored by: The FreeBSD Foundation
* Append the FILESGROUP rather than overritingbapt2015-03-151-1/+1
|
* Make at(1) and related tools an individual packagebapt2015-03-051-1/+7
|
* Honor MK_ACCT with etc/pam.d/atrunngie2015-01-261-1/+6
| | | | | MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
* - FreeBSD ships a KDE PAM module in base, but it's missing support for ↵miwi2012-05-301-1/+0
| | | | | | | | | | | passwordless login (kde-np), and it doesn't really belong in base system. PR: misc/167261 Submitted by: avilla@ Approved by: rwatson (mentor) MFC after: 3 days
* Remove gdm as it is no longer needed.marcus2009-07-181-1/+0
| | | | | Approved by: re (kib) Reminded by: nork
* Add PAM support to cron(8). Now cron(8) will skip commands scheduledyar2007-06-171-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Add PAM support to atrun(8).yar2007-06-151-0/+1
|
* Split the FILES list across multiple lines as in rc.d/Makefileyar2007-06-151-2/+14
| | | | | so that the change history stays easily readable as the number of PAM-aware services grows.
* Remove rexecd(8), a server that implements a particularly insecurenectar2005-06-101-1/+1
| | | | | | | method of executing commands remotely. There are no rexec clients in the FreeBSD tree, and the client function rexec(3) is present only in libcompat. It has been documented as "obsolete" since 4.3BSD, and its use has been discouraged in the man page for over 10 years.
* Start the dreaded NOFOO -> NO_FOO conversion.ru2004-12-211-1/+1
| | | | OK'ed by: core
* For variables that are only checked with defined(), don't provideru2004-10-241-1/+1
| | | | any fake value.
* Add a system policy, and have the login and su policies include it ratherdes2003-06-141-1/+1
| | | | | | than duplicate it. This requires OpenPAM Dianthus, which was committed two weeks ago; installing these files on a system running a world older than June 1st, 2003 will cause login(1) and su(1) to fail.
* Use the canonical form of installing links.ru2003-03-141-3/+1
| | | | | | Also, make "ftp" and "ftpd" hard links. Not objected to by: des
* There's no reason to have two identical policies for FTP servers, sodes2003-02-101-2/+5
| | | | make ftp a symlink to ftpd.
* We don't use this any more.des2002-06-191-1/+1
| | | | Sponsored by: DARPA, NAI Labs
* Add a PAM policy for rexecd(8).des2002-05-021-1/+1
| | | | Sponsored by: DARPA, NAI Labs
* Fixed bugs in previous revision:ru2002-04-181-20/+6
| | | | | | | | | | | | | 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
* Use ${FILES} and <bsd.prog.mk> rather than roll-your-own.des2002-04-181-22/+21
|
* Add PAM policy for the "passwd" service, including a sample config linedes2002-04-151-0/+1
| | | | | | for pam_passwdqc. Sponsored by: DARPA, NAI Labs
* Install pam.d files with mode 0644, not 0755.des2001-12-061-1/+1
|
* Makefile for pam.d configuration files.des2001-12-061-0/+24
Sponsored by: DARPA, NAI Labs
OpenPOWER on IntegriCloud