Bug 87455 - pam_unix remember= parameter produces errors
Summary: pam_unix remember= parameter produces errors
Keywords:
Status: CLOSED DUPLICATE of bug 127524
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pam
Version: 8.0
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-03-27 01:15 UTC by Adam Wiggins
Modified: 2015-01-08 00:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:52:22 UTC


Attachments (Terms of Use)

Description Adam Wiggins 2003-03-27 01:15:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207
Phoenix/0.5

Description of problem:
Trying to use the remember= parameter of the pam_unix.so module to store past
passwords in /etc/opasswd produces the following.  I modified
/etc/pam.d/system-auth to contain:

password    required      /lib/security/pam_cracklib.so retry=3 type=
password    sufficient    /lib/security/pam_unix.so nullok use_authtok md5
shadow remember=3
password    required      /lib/security/pam_deny.so

Then when any user tries to change their password...

[test@ash test]$ passwd
Changing password for user test.
Changing password for test
(current) UNIX password:
New password:
Retype new password:
Password has been already used. Choose another.
Password has been already used. Choose another.
Password has been already used. Choose another.
passwd: Authentication token manipulation error
[test@ash test]$

I am quite certain that the password I am using has not been used before.  Plus,
there is /etc/opasswd!


Version-Release number of selected component (if applicable):
pam-0.75-46.8.0

How reproducible:
Always

Steps to Reproduce:
1. append remember=3 to line 11 of /etc/pam.d/system-auth
2. try to change a user's password with passwd


Additional info:

Comment 1 Need Real Name 2003-05-24 16:36:14 UTC
The fix is to touch /etc/security/opasswd.  This should probably be done by the
install process, doncha' think?

Comment 2 Jindrich Novy 2004-09-21 08:39:05 UTC

*** This bug has been marked as a duplicate of 127524 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:52:22 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.