| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
a warning if neither luser nor ruser is specified. The correct option
for su(1) is ruser.
MFC after: 1 month
|
|
|
|
|
| |
PR: misc/53293
Submitted by: ru
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Don't give examples of such use, this is bogus.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
session management services.
Sponsored by: DARPA, NAI Labs
|
|
|
|
| |
Sponsored by: DARPA, NAI Labs
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
twentyfour hours ago, except for RCS ids.
|
| |
|
| |
|
|
|
|
|
|
|
| |
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)
|
|
Sponsored by: DARPA, NAI Labs
|