2012/6/20 Francesco Belli Francesco.Belli@vegaspace.com:
Hi Clement, I already used pam_password directive, I set it to cleartext, but this parameter is used for password change and not for authentication. As man pam_ldap says "Specifies the password change protocol to use", so not the authentication method. Now my situation is that I have some users in the LDAP server that they have a SHA hash in the userPassword field, and they are correctly authenticated, others that have a clear text password and cannot be authenticated via PAM.
Password scheme used in LDAP directory do not prevent any application to authenticate to LDAP. Dig into logs to see what is the real reason of your problem.
Clément.
Sent: Wed Jun 20 2012 04:36:03 GMT-0400 (EDT) From: Clément OUDOT clem.oudot@gmail.com To: Francesco Belli Francesco.Belli@vegaspace.com openldap-technical@openldap.org Subject: Re: PAM authentication and PPolicy issues
2012/6/20 Francesco BelliFrancesco.Belli@vegaspace.com:
Hi Clement, I already used pam_password directive, I set it to cleartext, but this parameter is used for password change and not for authentication. As man pam_ldap says "Specifies the password change protocol to use", so not the authentication method. Now my situation is that I have some users in the LDAP server that they have a SHA hash in the userPassword field, and they are correctly authenticated, others that have a clear text password and cannot be authenticated via PAM.
Password scheme used in LDAP directory do not prevent any application to authenticate to LDAP. Dig into logs to see what is the real reason of your problem.
Clément.
In addition, it is not true that the password must be stored in cleartext for pwdCheckQuality and pwdInHistory to work. Storing passwords in cleartext is bad.
-Patrick
2012/6/20 Patrick Hemmer openldap@stormcloud9.net:
Sent: Wed Jun 20 2012 04:36:03 GMT-0400 (EDT) From: Clément OUDOT clem.oudot@gmail.com To: Francesco Belli Francesco.Belli@vegaspace.com openldap-technical@openldap.org
Subject: Re: PAM authentication and PPolicy issues
2012/6/20 Francesco Belli Francesco.Belli@vegaspace.com:
Hi Clement, I already used pam_password directive, I set it to cleartext, but this parameter is used for password change and not for authentication. As man pam_ldap says "Specifies the password change protocol to use", so not the authentication method. Now my situation is that I have some users in the LDAP server that they have a SHA hash in the userPassword field, and they are correctly authenticated, others that have a clear text password and cannot be authenticated via PAM.
Password scheme used in LDAP directory do not prevent any application to authenticate to LDAP. Dig into logs to see what is the real reason of your problem.
Clément.
In addition, it is not true that the password must be stored in cleartext for pwdCheckQuality and pwdInHistory to work. Storing passwords in cleartext is bad.
They can be stored hashed, but they must be sent as clear text in the modification operation so that OpenLDAP can check the quality (min size for example). The ppolicy overlay is then able to hash them when storing accepted password in database.
Clément.
Sorry Patric, Maybe the reference that I have is wrong, I'm using the book "Mastering OpenLDAP" by Matt Butcher that in chapter 6 at pag 323 says "if you store password in plain text in the directory then the policy overlay can be configured to maintain a password history". Now I'm using http://www.openldap.org/software/man.cgi?query=slapo-ppolicy&apropos=0&a... as reference for ppolicy. My authentication error was a trivial problem on an objectClass: posixAccount. Now I'm testing with SHA stored passwords the pwdInHistory directive. Thanks for the suggestions, Regards Francesco
From: openldap-technical-bounces@OpenLDAP.org [mailto:openldap-technical-bounces@OpenLDAP.org] On Behalf Of Patrick Hemmer Sent: 20 June 2012 14:17 To: openldap-technical@openldap.org Subject: Re: PAM authentication and PPolicy issues
Sent: Wed Jun 20 2012 04:36:03 GMT-0400 (EDT) From: Clément OUDOT clem.oudot@gmail.commailto:clem.oudot@gmail.com To: Francesco Belli Francesco.Belli@vegaspace.commailto:Francesco.Belli@vegaspace.com openldap-technical@openldap.orgmailto:openldap-technical@openldap.org Subject: Re: PAM authentication and PPolicy issues
2012/6/20 Francesco Belli Francesco.Belli@vegaspace.commailto:Francesco.Belli@vegaspace.com:
Hi Clement,
I already used pam_password directive, I set it to cleartext, but this parameter is used for password change and not for authentication. As man pam_ldap says "Specifies the password change protocol to use", so not the authentication method. Now my situation is that I have some users in the LDAP server that they have a SHA hash in the userPassword field, and they are correctly authenticated, others that have a clear text password and cannot be authenticated via PAM.
Password scheme used in LDAP directory do not prevent any application
to authenticate to LDAP. Dig into logs to see what is the real reason
of your problem.
Clément. In addition, it is not true that the password must be stored in cleartext for pwdCheckQuality and pwdInHistory to work. Storing passwords in cleartext is bad.
-Patrick
On Wed, Jun 20, 2012 at 01:44:05PM +0000, Francesco Belli wrote:
Now I’m using http:// www.openldap.org/software/man.cgi?query=slapo-ppolicy&apropos=0&sektion=5& manpath=OpenLDAP+2.3-Release&format=html as reference for ppolicy. My
The 2.3 release series is very old now. You should be using 2.4 and the 2.4 manuals:
http://www.openldap.org/software/man.cgi
I’m testing with SHA stored passwords the pwdInHistory directive.
SHA is much better than plaintext, but best practice is to use a salted hash - SSHA in this case. The use of salt frustrates attempts to build a dictionary to invert stolen password records. If LinkedIn had used salt in their password hashes they would now be in less trouble as a result of the recent disclosure...
https://community.qualys.com/blogs/securitylabs/2012/06/08/lessons-learned-f...
Andrew
openldap-technical@openldap.org