On Tue, Jun 04, 2013 at 10:49:27PM -0500, cbul...@gmail.com wrote:
We are already using overlay and it is working perfectly.
Your point about MD5 is great!...but we have some requirements and the
idea is use SSHA-512 for our password.
I read some post from Michael talking about this problem
cbul...@gmail.com wrote:
Thanks for your prompt reply.
We are not using any client..
If you change passwords via LDAP there *is* a LDAP client.
we are just changing the user password from
ssh console.
So the client is whatever your PAM configuration has for passwd,e.g. pam_ldap,
sssd etc.
On Mon, Jun 03, 2013 at 03:54:38PM -0500, cbul...@gmail.com wrote:
We are not using any client..we are just changing the user password from
ssh console.
If you use the passwd command, the LDAP operation used to make the change
will depend on your PAM LDAP implementation. It might be the
Hi Andrew and Michael,
Thanks so much for your clarificationI really appreciate them.
We are already using overlay and it is working perfectly.
Your point about MD5 is great!...but we have some requirements and the
idea is use SSHA-512 for our password.
I read some post from Michael talking
Hi,
All our users in LDAP database are under MD5 encryption. We want to
change this to SSHA in the next user password change.
We tried using: password-hash {SSHA} option in slapd.conf and restart
the ldap service but it didn't work. The user password are still under
MD5 encryption.
We are using
cbul...@gmail.com wrote:
All our users in LDAP database are under MD5 encryption. We want to
change this to SSHA in the next user password change.
We tried using: password-hash {SSHA} option in slapd.conf and restart
the ldap service but it didn't work. The user password are still under
MD5
Hi Michael,
Thanks for your prompt reply.
We are not using any client..we are just changing the user password from
ssh console.
We imported our /etc/passwd to openldap and our idea is when the user
gets the next expiration time the new password be in SSHA.
Is it possible?
Thanks!
On