summaryrefslogtreecommitdiff
path: root/modules/pam_unix
Commit message (Collapse)AuthorAge
* Relevant BUGIDs: noneThorsten Kukuk2005-05-16
| | | | | | | | | Purpose of commit: new feature Commit summary: --------------- Add SELinux support, based on Patch from Red Hat
* Relevant BUGIDs:Tomas Mraz2005-04-12
| | | | | | | | Purpose of commit: bugfix Commit summary: --------------- pam_unix: nis option shouldn't clear the shadow option
* Relevant BUGIDs: Red Hat bz #88127Tomas Mraz2005-04-08
| | | | | | | | | Purpose of commit: Commit summary: --------------- pam_unix: fix regression introduced in 0.78 - both NIS and local password should be changed if possible - see the analysis in the RH bugzilla
* Relevant BUGIDs: -Tomas Mraz2005-03-23
| | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Improve LSB-2.0 compliance
* Relevant BUGIDs: 872943Thorsten Kukuk2005-01-10
| | | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Fix return value for unknown user (This is PAM_USER_UNKNOWN and not PAM_AUTHINFO_UNAVAIL).
* Relevant BUGIDs: 872945Thorsten Kukuk2005-01-05
| | | | | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Calling pam_chauthtok of pam_unix and entering the correct old password, but abort on typing the new one, PAM_AUTHTOK_RECOVER_ERR is returned. Since we got the old token, PAM_AUTHTOK_ERR needs to be returned. Found by LSB PAM testsuite.
* Relevant BUGIDs: Red Hat bz 120694Tomas Mraz2005-01-04
| | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- skip logging of 'user unknown' authentication failure if the user has passwd entry
* Relevant BUGIDs: Red Hat bz 139539Tomas Mraz2004-12-03
| | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Rearrange conditions in pam_unix_acct to make it more reliable with large values of expiration times.
* Relevant BUGIDs: Red Hat bz 140451Tomas Mraz2004-11-23
| | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Convert uid gid from passwd entry always as decimal. Test failure.
* Relevant BUGIDs: Redhat bz 69279Tomas Mraz2004-11-17
| | | | | | | | Purpose of commit: bugfix Commit summary: --------------- pam_unix: Forced password change shouldn't trump account expiration
* Applied debian patchesSebastien Tricaud2004-11-16
|
* Relevant BUGIDs: Red Hat bz 77646Tomas Mraz2004-11-11
| | | | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Test return value of renames for failure so user knows that his password wasn't really changed. Also report error when /etc/security/opasswd is missing and pam_unix module is called with remember=x.
* Relevant BUGIDs:Tomas Mraz2004-11-11
| | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- I've forgot to remove some selinux specific part when changing locking in pam_unix_passwd
* Relevant BUGIDs: Redhat BZ 115309Tomas Mraz2004-11-10
| | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Change the order of password change (first try local, then NIS)
* Relevant BUGIDs:Thorsten Kukuk2004-11-08
| | | | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Fix make clean for pam_unix (remove bigcrypt binary)
* Relevant BUGIDs:Tomas Mraz2004-11-04
| | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Fix locking in pam_unix_passwd to avoid race on changing passwords
* Relevant BUGIDs:Thorsten Kukuk2004-10-06
| | | | | | | | | Purpose of commit: Commit summary: --------------- bugfix: Last part of fixes from Red Hat
* Relevant BUGIDs:Thorsten Kukuk2004-09-30
| | | | | | | | | Purpose of commit: Commit summary: --------------- bugfix: Preserve permissions of shadow/passwd file. From Red Hat.
* Relevant BUGIDs:Thorsten Kukuk2004-09-28
| | | | | | | | | | | | Purpose of commit: Commit summary: --------------- bugfix: * Merge patches from Red Hat (Bug 477000 and other - kukuk) * Fix pam_rhosts option parsing (Bug 922648 - kukuk)
* Relevant BUGIDs:Thorsten Kukuk2004-09-24
| | | | | | | | | | Purpose of commit: Commit summary: --------------- bugfix: 440107: Add various patches from Linux Distibutors to make PAM modules reentrant.
* Relevant BUGIDs:Thorsten Kukuk2004-09-24
| | | | | | | | | | | Purpose of commit: Commit summary: --------------- bugfix: Fix lot of compiler warnings new feature: add broken_shadow option to pam_unix (patch from Linux distributions)
* Relevant BUGIDs:Thorsten Kukuk2004-09-22
| | | | | | | | | Purpose of commit: Commit summary: --------------- bugfix: Add rest of Steve Grubb's resource leak and other fixes
* Relevant BUGIDs:Thorsten Kukuk2004-09-15
| | | | | | | | | Purpose of commit: Commit summary: --------------- bugfix: Add parts of Steve Grubb's resource leak and other fixes
* Relevant BUGIDs:Thorsten Kukuk2004-09-14
| | | | | | | | | Purpose of commit: Commit summary: --------------- bugfix: Bug 1027903 and 1027912
* Relevant BUGIDs: 849498Thorsten Kukuk2003-11-26
| | | | | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- The type of remember in support.c is int, not long. But we compare remember with LONG_MIN and LONG_MAX. While this works on 32bit architectures, this fails on 64bit one. INT_MIN and INT_MAX should be used.
* Relevant BUGIDs: 643357Steve Langasek2003-07-13
| | | | | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Patch from Sam Hartman to fix handling of module linking on Linux: modules should be linked against libpam if they call any functions from the library, since not all platforms will correctly resolve symbol references otherwise. Also, make sure we use gcc, not ld, when linking, since there's additional linker glue that gcc will pull in for us.
* Relevant BUGIDs: patch 476976Steve Langasek2003-07-13
| | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Patch from Nalin Dahyabhai: when updating /etc/{passwd,shadow}, always respect any admin-specified permissions on the existing files.
* Relevant BUGIDs: 667584 664290Andrew G. Morgan2003-01-14
| | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Two bug fixes in one: don't trust getlogin() and sanely lower the time the password databases are locked in pam_unix.
* Relevant BUGIDs: 521314Andrew G. Morgan2002-09-23
| | | | | | | | Purpose of commit: bugfix Commit summary: --------------- This code is needed to complete this bugfix.
* Relevant BUGIDs: 476963Andrew G. Morgan2002-07-11
| | | | | | | | | | | | Purpose of commit: new feature Commit summary: --------------- some applications are not prepared to get a SIGCHLD from a child process they didn't think they launched, so we now suppress this signal for the duration of use of the helper binary. The 'noreap' module argument is provided to override this new default.
* Relevant BUGIDs: 521314Andrew G. Morgan2002-07-09
| | | | | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- bigcrypt does not match crypt when password length is too long. This led to a pam_unix problem when the module had not set the password in bigcrypt mode, but was trying to compare with bigcrypt output. The fix is to use the stored password as a guide to how much of the encrypted password to compare against.
* Relevant BUGIDs: 476971Andrew G. Morgan2002-05-29
| | | | | | | | Purpose of commit: documentation Commit summary: --------------- typo/correctness fixes from Nalin.
* Relevant BUGIDs: 517743Andrew G. Morgan2002-05-07
| | | | | | | | Purpose of commit: bugfix Commit summary: --------------- pam_pwdb did it, so make pam_unix log when a passowrd is changed.
* Relevant BUGIDs: 507379Andrew G. Morgan2002-02-08
| | | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- there were some dangling file descriptors and unclear pass/fail properties of some of the password updating code in pam_unix. Bug report from Len Lattanzi.
* Relevant BUGIDs: 486361Andrew G. Morgan2001-12-09
| | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- pam_unix is too generic a module to override the PAM_USER_PROMPT item. (More modifications to xsh to help me test this change.)
* Relevant BUGIDs: 485454Andrew G. Morgan2001-12-09
| | | | | | | | | Purpose of commit: cleanup Commit summary: --------------- The malloc debugging stuff appears to have had a few residual issues that I've fixed (trying to resolve another checkin!).
* Relevant BUGIDs: 483959Steve Langasek2001-11-30
| | | | | | | | Purpose of commit: bugfix Commit summary: --------------- pam_unix: fix 'likeauth' to kill off the memory leak once and for all.
* Relevant BUGIDs: 483959, 113596Steve Langasek2001-11-27
| | | | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- * Restore pam_unix's handling of 'likeauth' argument to a known working state * prettify AUTH_RETURN macro * remove redundant argv checks in pam_sm_setcred()
* Relevant BUGIDs: 476949Andrew G. Morgan2001-11-27
| | | | | | | | Purpose of commit: documentation fixes Commit summary: --------------- Fix some typos noted by Nalin.
* Relevant BUGIDs: 483959Andrew G. Morgan2001-11-27
| | | | | | | | | Purpose of commit: fix memory leak Commit summary: --------------- Fernando Trias pointed out a silly memory leak in pam_unix.so. It looks like some allocated memory that is simply not needed for anything.
* Relevant BUGIDs: 476947Andrew G. Morgan2001-11-26
| | | | | | | | | Purpose of commit: cleanup Commit summary: --------------- be more confident that strings are being initialized correctly from Nalin.
* Relevant BUGIDs: 440107Steve Langasek2001-09-13
| | | | | | | | | Purpose of commit: module reentrancy Commit summary: --------------- Commit sample code that uses getpwnam_r instead of getpwnam. All code is #ifdef'ed out right now.
* Relevant BUGIDs: 440107Steve Langasek2001-09-13
| | | | | | | | | Purpose of commit: module reentrancy Commit summary: --------------- Commit sample code that uses getpwnam_r instead of getpwnam. All code is #ifdef'ed out right now.
* Relevant BUGIDs: 461089Andrew G. Morgan2001-09-13
| | | | | | | | Purpose of commit: cleanup Commit summary: --------------- remove a compilation warning.
* Relevant BUGIDs: 440107Steve Langasek2001-07-10
| | | | | | | | | | Purpose of commit: bugfix/cleanup Commit summary: --------------- Removed superfluous use of static variables in md5 and bigcrypt routines, bringing us a step closer to thread-safeness. Eliminated some variable indirection along the way.
* Relevant BUGIDs: 419803Steve Langasek2001-04-28
| | | | | | | | Purpose of commit: bugfix Commit summary: --------------- Fix pam_unix to not zero out password strings that it doesn't own!
* Relevant BUGIDs: 112540Andrew G. Morgan2001-02-11
| | | | | | | | | | | | | | | Purpose of commit: minor security bugfix Commit summary: --------------- Fixes for the password helper binaries. Before, there was no check that the password entered was actually that of the intended user being authenticated. Instead, the password was checked for the requesting user. While this disstinction sounds like a security hole, its actually not been a problem in practice. The helper binaries have only been used in the case that the application is not setuid-0 and as such even if an improper authentication succeeded, the application could not change its uid from that of the requesting user.
* Relevant BUGIDs: 127700Andrew G. Morgan2001-01-20
| | | | | | | | | Purpose of commit: bugfix Commit summary: --------------- ia64 support - it behaves like an alpha wrt md5, but then unsigned int is 32 bits everywhere(*) these days, so just remove the #ifdef nonsense.
* Relevant BUGIDs: 126431, 126423Steve Langasek2000-12-20
| | | | | | | | | | | | Purpose of commit: new feature / bugfix Commit summary: --------------- This changes the format of pam_unix log messages, per bug 126423. The change is extensive (every call to _log_err() now has an additional argument) but straightforward. These changes to the logging code incidentally fix the problem reported in bug 126431.
* Relevant BUGIDs: 126036Steve Langasek2000-12-18
| | | | | | | | | | | | | | | Purpose of commit: cleanup Commit summary: --------------- Changes format of pam_unix 'authentication failure' log messages for purposes of consistency and clarity. Note that we do not log the 'user=' item in the case of an invalid username unless the audit flag is turned on. Note also that the way we currently log these failures isn't i18n-friendly. I imagine this will need correcting at some point in the future.