summaryrefslogtreecommitdiffstats
path: root/etc/pam.d
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
* Fix xref, pam(8) -> pam(3)gavin2014-08-261-1/+1
| | | | | | PR: 193045 Submitted by: rsimmons0 gmail com MFC after: 3 days
* - FreeBSD ships a KDE PAM module in base, but it's missing support for ↵miwi2012-05-302-20/+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
* Forgot to commit this change along with r219563: pam_group(8) now issuesdes2011-03-151-1/+1
| | | | | | | a warning if neither luser nor ruser is specified. The correct option for su(1) is ruser. MFC after: 1 month
* tabifydes2009-10-057-14/+14
| | | | MFC after: 3 weeks
* Change the pam_ssh examples: if you use it, you probably want want_agent.des2009-10-055-5/+5
| | | | MFC after: 3 weeks
* Remove gdm as it is no longer needed.marcus2009-07-181-1/+0
| | | | | Approved by: re (kib) Reminded by: nork
* Remove this file. It is no longer needed as x11/gdm provides its ownmarcus2009-07-181-19/+0
| | | | | | version under /usr/local/etc/pam.d. Approved by: re (kib)
* Add PAM support to cron(8). Now cron(8) will skip commands scheduledyar2007-06-172-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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-152-0/+11
|
* Locked out and expired accounts shouldn't be accessible via remoteyar2007-06-152-0/+2
| | | | | mailbox protocols. Add pam_unix to the `account' function class, too, for imap and pop3 to actually implement this policy.
* 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.
* Now pam_nologin(8) will provide an account management functionyar2007-06-1011-11/+15
| | | | | | | | | | | | | | | | | | | | | | | 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
* Remove rexecd(8), a server that implements a particularly insecurenectar2005-06-102-20/+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.
* X logins should be recorded in lastlog / wtmp / utmp. I have no idea whydes2005-04-281-1/+1
| | | | | | this wasn't there already... it makes much more sense this way. MFC after: 2 weeks
* 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.
* Removed whitespace at BOF, EOL & EOF.schweikh2004-06-062-6/+6
|
* the default password policy for xdm should be pam_deny, since it isdes2004-02-201-0/+3
| | | | incapable of holding a meaningful conversation.
* Don't do session management in su.des2003-07-091-1/+1
| | | | | PR: misc/53293 Submitted by: ru
* Add a system policy, and have the login and su policies include it ratherdes2003-06-144-23/+35
| | | | | | 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.
* Try to describe the control flags a little better.des2003-06-011-2/+4
|
* The PAM module pam_krb5 does not have "session" capabilities.markm2003-04-309-9/+0
| | | | Don't give examples of such use, this is bogus.
* Add nullok to the pam_unix line.des2003-04-241-1/+1
|
* Use the canonical form of installing links.ru2003-03-141-3/+1
| | | | | | Also, make "ftp" and "ftpd" hard links. Not objected to by: des
* Initiate KerberosIV de-orbit burn. Disconnect the /etc configs.markm2003-03-0811-32/+0
|
* Add the allow_local option to all pam_opieaccess entries.des2003-02-166-6/+6
|
* Add the want_agent option to the commented-out "session" pam_ssh entry.des2003-02-161-1/+1
|
* Major cleanup & homogenization.des2003-02-1014-131/+150
|
* No idea what this is for, and it doesn't make much sense. If a port needsdes2003-02-101-8/+0
| | | | it, it can install its own copy in /usr/local/etc/pam.d/.
* There's no reason to have two identical policies for FTP servers, sodes2003-02-102-26/+5
| | | | make ftp a symlink to ftpd.
* Use pam_group(8) instead of pam_wheel(8).des2003-02-061-1/+1
|
* Don't enable pam_krb5 by default - most people don't have it since mostdes2003-02-031-2/+2
| | | | | | | people don't build with MAKE_KERBEROS5 defined. Provide commented-out usage examples instead, like we do everywhere else. Pointy hat to: des
* Enable pam_krb5 for sshd. I've had this in my tree for ages.des2003-02-021-0/+2
|
* Since OpenSSH drops privileges before calling pam_open_session(3),des2002-12-031-1/+1
| | | | | | pam_lastlog(8) can't possibly work, so let OpenSSH handle lastlog. Approved by: re (rwatson)
* Exempt the "wheel group requirement" by default when su'ing to root ifrwatson2002-10-181-1/+1
| | | | | | | | | | the wheel group has no explicit members listed in /etc/group. This adds the "exempt_if_empty" flag to pam_wheel in the default configuration; in some environments, it may be appropriate to remove this flag, however, this default is the same as pre-pam_wheel. Reviewed by: markm Sponsored by: DARPA, Network Associates Laboratories
* Silence pam_lastlog for now.des2002-07-071-1/+1
|
* We don't use this any more.des2002-06-192-10/+1
| | | | Sponsored by: DARPA, NAI Labs
* Enable OPIE for sshd and telnetd. I thought I'd done this a long timedes2002-06-192-0/+4
| | | | | | ago... Sponsored by: DARPA, NAI Labs
* Use pam_lastlog(8)'s new no_fail option.des2002-05-083-3/+3
| | | | Sponsored by: DARPA, NAI Labs
* Add a PAM policy for rexecd(8).des2002-05-022-1/+17
| | | | Sponsored by: DARPA, NAI Labs
* xdm plays horrid tricks with PAM, and dumps core if it's allowed to calldes2002-05-022-0/+2
| | | | | | | | pam_lastlog, so add a dummy session chain to avoid using the one from pam.d/other. I assume gdm does something similar, so give it a dummy session chain as well. Sponsored by: DARPA, NAI Labs.
* Add no_warn to pam_lastlog. This should prevent xdm from dumping coredes2002-04-291-1/+1
| | | | when linked with Linux-PAM.
* Don't list pam_unix in the session chain, since it does not provide anydes2002-04-189-11/+1
| | | | | | session management services. 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-152-0/+12
| | | | | | for pam_passwdqc. Sponsored by: DARPA, NAI Labs
OpenPOWER on IntegriCloud