Submitted by SeaHawk on Wed, 05/30/2012 - 00:22
System using LDAP
Users report error when trying to change password from webmail...
root@hosting:/etc/pam.d# /usr/share/webmin/virtual-server/change-password.pl Username: karen Old password: (oldpwd) New password: (newpwd) Wrong password
root@hosting:/etc/pam.d# passwd karen New password: Re-enter new password: LDAP password information changed for karen passwd: password updated successfully
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Wed, 05/30/2012 - 02:00 Comment #1
This might be due to the LDAP server returning passwords with an encryption type prefixed that Virtualmin doesn't understand..
If you run the command :
virtualmin list-users --domain example.com --user karen --multiline
what does it output? Replace example.com above with the actual domain name for user karen.
Submitted by SeaHawk on Wed, 05/30/2012 - 16:14 Comment #2
root@hosting:~# virtualmin list-users --domain beeze.com --user karen --multiline
karen
Domain: beeze.com
Unix username: karen
Real name: Karen Scott
Encrypted password: $1$D35iL.XX$013roN3xd.HOfcby01HwZ0
Disabled: No
Home directory: /home/beeze/homes/karen
FTP access: No
Login permissions: Email only
Shell: /dev/null
User type: Normal user
Home quota: Unlimited
Home quota used: 713.72 MB
Home byte quota: 0
Home byte quota used: 748388352
Mail location: /home/beeze/homes/karen/Maildir
Mail storage type: Maildir
Email address: karen@beeze.com
Extra addresses: karen.scott@beeze.com
Check spam and viruses: Yes
Last logins: smtp 24/May/2012 08:59, imap 30/May/2012 06:05
(Password last changed with Virtualmin -> Edit Users function)
Submitted by JamieCameron on Wed, 05/30/2012 - 16:31 Comment #3
Ok, I see the issue here .. when the MD5 salt contains a dot (as it does in this case), Virtualmin isn't doing the hashing correctly to validate the old password. I'll fix this in the next Webmin release.
Submitted by SeaHawk on Wed, 05/30/2012 - 16:41 Comment #4
Noted and will inform users... Thanks :)
Submitted by Issues on Wed, 06/13/2012 - 16:45 Comment #5
Automatically closed -- issue fixed for 2 weeks with no activity.