[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
use proprietary password hash in "userpassword"
- To: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
- Subject: use proprietary password hash in "userpassword"
- From: Meike Stone <meike.stone@googlemail.com>
- Date: Thu, 19 Jan 2017 12:25:38 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=sHyql0aW3JPvAxgyrh0Oa3sCtrRdkyJFifKX2VBqbe0=; b=NEUysKlJOuvnTu80Us+a9zsQqZAvUJsEkqn/H1iCqOe7wJ8Iajg78fV8cHFs40zpwb uXeaRlLdvMjHlmCnDbQDpR1OmincdAAe9mdPBznY/YDp2t7dmBGtGd7S5wR1lzSxLwzt jsd13iR+atLFhaCR5cjd4XaLW+2yb/Dnwn/slbnNDnunjZodVz0Se+JBXOvak1nFNmGB vh3vAyTW3T4aF0HTLl0lVx36DTAJMaU92Xj0x55loTlGYmYBaI+8VDv7gCQOkgK0WYIA o97Y70b0n7t1Dn4kvWfNyDA+XWWwCN23TlvK+EMSSWxNvrGuVNVd0gJZiInYMrRF8118 mmow==
Hello dear list,
we like to migrate an a user database from SQL to LDAP and need to
take over the user passwords.
Problem is, the passwords are hashed by an known but proprietary algorithm.
Is there a possibility, to write an small external binary, that is
used by slapd to validate these passwords? (Maybe, we import that in a
own attribute?)
After password change, we want write a ssha hash, so that we can
disable this external binary...
Write a openldap modul like pw-sha2 is not the first choice, because
we need to compile the openldap after each update on our own and that
prevents us to use the distribution packages.
Thanks for help,
kindly regards
Meike