[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: { in cleartext passwords

To: l0calh0st <127.0.0.1x@gmail.com>
Subject: Re: { in cleartext passwords
From: Howard Chu <hyc@symas.com>
Date: Tue, 23 Aug 2005 17:19:21 -0700
Cc: openldap-software@OpenLDAP.org
In-reply-to: <de7162cc05082315193f3f8989@mail.gmail.com>
References: <de7162cc05082315193f3f8989@mail.gmail.com>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050821 SeaMonkey/1.0a

l0calh0st wrote:

Hi:
Over the weekend, I upgraded our 4 server environment from ldbm-backend 2.0.23 on RedHat 7.1 to bdb-backend 2.2.23 on Debian Sarge. Things went quite swimmingly, but I am noticing issues with some of our users that have { as the first character in their password. We store the passwords in cleartext in the database, and my workaround has been to convert the affected folks' passwords to {CRYPT} hashes, but I think it is only a feasible temporary solution, as our password programming application will eventually pick an incompatible password.

You should be able to prefix the password with "{CLEARTEXT}" to get by this problem.

--
 -- Howard Chu
 Chief Architect, Symas Corp.  http://www.symas.com
 Director, Highland Sun        http://highlandsun.com/hyc
 OpenLDAP Core Team            http://www.openldap.org/project/

References:
- { in cleartext passwords
  - From: l0calh0st <127.0.0.1x@gmail.com>

Prev by Date: Re: LDAP Replication/update dn entry
Next by Date: Re: LDAP Replication/update dn entry
Index(es):
- Chronological
- Thread