- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

- FreeBSD ships a KDE PAM module in base, but it's missing support for 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 issues
a warning if neither luser nor ruser is specified. The correct option
for su(1) is ruser.

MFC after: 1 month

tabify

MFC after: 3 weeks

Change the pam_ssh examples: if you use it, you probably want want_agent.

MFC after: 3 weeks

Remove gdm as it is no longer needed.

Approved by: re (kib)
Reminded by: nork

Remove this file. It is no longer needed as x11/gdm provides its own
version under /usr/local/etc/pam.d.

Approved by: re (kib)

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

Add PAM support to atrun(8).

Locked out and expired accounts shouldn't be accessible via remote
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/Makefile
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 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

Remove rexecd(8), a server that implements a particularly insecure
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 why
this wasn't there already... it makes much more sense this way.

MFC after: 2 weeks

Start the dreaded NOFOO -> NO_FOO conversion.

OK'ed by: core

For variables that are only checked with defined(), don't provide
any fake value.

Removed whitespace at BOF, EOL & EOF.

the default password policy for xdm should be pam_deny, since it is
incapable of holding a meaningful conversation.

Don't do session management in su.

PR: misc/53293
Submitted by: ru

Add a system policy, and have the login and su policies include it rather
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.

The PAM module pam_krb5 does not have "session" capabilities.
Don't give examples of such use, this is bogus.

Add nullok to the pam_unix line.

Use the canonical form of installing links.
Also, make "ftp" and "ftpd" hard links.

Not objected to by: des

Initiate KerberosIV de-orbit burn. Disconnect the /etc configs.

Add the allow_local option to all pam_opieaccess entries.

Add the want_agent option to the commented-out "session" pam_ssh entry.

Major cleanup & homogenization.

No idea what this is for, and it doesn't make much sense. If a port needs
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, so
make ftp a symlink to ftpd.

Use pam_group(8) instead of pam_wheel(8).

Don't enable pam_krb5 by default - most people don't have it since most
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.

Since OpenSSH drops privileges before calling pam_open_session(3),
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 if
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.

We don't use this any more.

Sponsored by: DARPA, NAI Labs

Enable OPIE for sshd and telnetd. I thought I'd done this a long time
ago...

Sponsored by: DARPA, NAI Labs

Use pam_lastlog(8)'s new no_fail option.

Sponsored by: DARPA, NAI Labs

Add a PAM policy for rexecd(8).

Sponsored by: DARPA, NAI Labs

xdm plays horrid tricks with PAM, and dumps core if it's allowed to call
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 core
when linked with Linux-PAM.

Don't list pam_unix in the session chain, since it does not provide any
session management services.

Sponsored by: DARPA, NAI Labs

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

Use ${FILES} and <bsd.prog.mk> rather than roll-your-own.

Add PAM policy for the "passwd" service, including a sample config line
for pam_passwdqc.

Sponsored by: DARPA, NAI Labs

Add pam_lastlog(8) here since I removed lastlog support from sshd.

Sponsored by: DARPA, NAI Labs

Use pam_rhosts(8).

If used, pam_ssh should be marked "sufficient", not "required".

Sponsored by: DARPA, NAI Labs

Switch over to using pam_login_access(8) module in sshd(8).
(Fixes static compilation. Reduces diffs to OpenSSH.)

Reviewed by: bde

Add missing "nullok" option to pam_unix.

Add pam_self(8) so users can login(1) as themselves without authentication,
pam_login_access(8) and pam_securetty(8) to enforce various checks
previously done by login(1) but now handled by PAM, and pam_lastlog(8) to
record login sessions in utmp / wtmp / lastlog.

Sponsored by: DARPA, NAI Labs

Use pam_self(8) to allow users to su(1) to themselves without authentication.

Sponsored by: DARPA, NAI Labs

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

Really back out ache's commits. These files are now precisely as they were
twentyfour hours ago, except for RCS ids.

Back out recent changes

Turn on pam_opie by default. It should not affect non-OPIE users.

Turn on pam_opie by default. It not affect non-OPIE users

Previous commit was incomplete, use
"[default=ignore success=done cred_err=die]"
options instead of "required"

Remove explaining comment and pam_unix commented out, now pam_unix can be
chained with pam_opie

Change comment since fallback provided now not by ftpd but by pam_opie

Unmunge the version preservation code and obfuscate it so CVS won't munge
it all over again.

Back out previous commit, which erroneously removed essential comments. I
definitely need coffee.

Apologies to: ache

Update copyright

Sync with pam.conf revision 1.25.

Preserve FreeBSD version strings in target files.

Improve pam_unix/opie related ftpd comment even more

Clarify comment about pam_unix fallback for ftpd

Turn on pam_opie.so for ftpd by default
It not affect non-OPIE users

Install pam.d files with mode 0644, not 0755.

Makefile for pam.d configuration files.

Sponsored by: DARPA, NAI Labs

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)

pam.d-style configuration, auto-generated from pam.conf.

Sponsored by: DARPA, NAI Labs

Short README for /etc/pam.d, mostly extracted from the comments in pam.conf.

Perl script that splits pam.conf into separate files suitable for pam.d.

Sponsored by: DARPA, NAI Labs