I have a CentOS 5.4 mail server box (with postfix, dovecot and squirrelmail).
My problem:
- I create a user (example:) user
- I set the password (example:) password1234
…when i log-in to CentOS i must supply pass password1234 but when i log in to my mailbox (useing squirrelmail or MS Outlook) i only need to supply the first 8 characters of my password (example: "password" instead of "password1234")…
I`ve read that is a password encription thing (not md5?!) but where (postfix? squirrelmail? dovecot?) and how i can correct this ???
I don't think that should happen since password1234 and password generates two unique hashes. The only scenario I can think of where this can occur is when you are using MySQL, and the password is stored in plaintext, and the field is defined as having a maximum length of 8.
Your password hash is probably DESCRYPT which has a maximum length of 8. The default for Linux installations is MD5. Run the Authentication application found in System > Administration. The password hashing algorithm can be found in the Options tab.
Post edited 5:44 pm – May 14, 2010 by daniel.bucur
ty again, but:
i double-checked that setting and it`s for sure MD5
anyway, like i said: when logging on to CentOS i must supply full password (example: password1234) the problem appears when i login via mail client (squirrelmail or Outllok)…
I think that CentOS and mail client resolve authentication in different ways ?!?! Maybe useing different files ???
…or maybe … a misconfiguration in squirrelmail Change Password Plugin ???
Post edited 5:36 am – May 18, 2010 by daniel.bucur
Hey, consultant….
I think i guided you on wrong path….
…sorry!!!
i can logon to CentOS useing password (instead of password1234) ….
the misunderstanding (my misunderstanding) appeared becouse I setup root an user password the same (example: password1234) the only difference was that i setup password for user "user" via squirrelmail (Change Password plugin).
Tests i`ve did:
reset user "user" password to "password1234" via CentOS (System-> Administration -> Users and Groups)
i`ve tried to login to CentOS via user "user" and password "password" : didn`t work
i`ve tried to login to CentOS via user "user" and password "password1234" : it worked
i`ve tried to login to mail server via web interface (squirrelmail) useing "user" and "password" : didn`t work
i`ve tried to login to mail server via web interface (squirrelmail) useing "user" and "password1234" : it worked
So far i think it`s clear that it was Change Password plugin (for squirrelmail) fault
I`ve continued:
change user`s "user" password to "password1111" via web interface (squirrelmail and Change Password PlugIn)
logout (from web interface)
login useing (via web interface) "password": it worked
So far i think it`s verryclear that it was Change Password plugin (for squirrelmail) fault
I`ve continued (to check how was CentSO affected):
login to CentOS useing "user" and"password" : it worked
login to CentOS useing "user" and "password1111" : to my surprize: it worked
Now it`s a blur again…
not so verry clear…
Q: If CentOS is useing MD5 it should work in just one case: either "password" or "password1111" not both…Isn`t that so ? And what is wrong with Change Password plugin ?…
i think…. CentOS is useing 2 files to auth users…its his fault not dovecots…
PS:
i`ve tried lo login to CentOS useing a password in between (not 8 chr, not full pass) like "password11" : it worked
So… i thing that CentOS is showing MD5 but it`s useing DESCRYPT…
See SquirrelMail Change Password Howto article. I had an old SquirrelMail change password article but it had so many problems that I deleted it. That could be another one of its problem because the plugin uses an executable that writes the password hash directly into the password file. Thus it causes loads of problems like triggering an SELinux error, not updating the password modification date, etc. The new article above uses poppassd instead which solves all of the problems mentioned.
I`ve tested the new configuration al the ways i can think on. All are fine !!!
Still… if i may…
How you fix it ??? Between my post and your reply i google it alot and i din`t find relevant help/ documentation about poppassd daemon/service…
PS:
Great site you have here! love it! maybe in the near future i will folow your example and i will develop a site with the subjects that i have knoledge about!
Occasionally, when a read linux documentation, i invariably encounter paragraphs where are enumerate linux advantages and one of the main advantages is: continuous and fast developement by support of community.
When you mentioned that the problem occurs after changing the password via poppassd, I immediately knew it is a poppassd configuration problem. Poppassd uses the pluggable authentication module (PAM) so I just looked at the file /etc/pam.d/system-auth which is being used by the login module and bingo, it has md5 shadow in it.
Subscribe |
Follow me
Login 
Register 
Search 
Home
Reply to Post
Add a New Topic
Quote and Reply 
Topic RSS 
