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

Re: Double colon in LDIF

To: Owen DeLong <owen@delong.com>
Subject: Re: Double colon in LDIF
From: Mike Jackson <mj@sci.fi>
Date: Wed, 09 Mar 2005 21:23:15 +0200
Cc: rob fielding <rob@dsvr.net>, openldap-software@OpenLDAP.org
In-reply-to: <2147483647.1110296163@imac-en0.delong.sj.ca.us>
References: <1110280832.9899.53.camel@localhost.localdomain> <2147483647.1110296163@imac-en0.delong.sj.ca.us>
User-agent: Mozilla Thunderbird 0.7.3 (X11/20040803)

Owen DeLong wrote:

I don't know about NS Dir., but, in OpenLDAP, those represent values
that are already server-encrypted.  It's how the server differentiates
between:

userPassword: mypasswordintheclear
userPassword: {md5}anmd5hash
userPassword:: base64alreadyserverencryptedpassword

Huh? That last userPassword value does not signify that it is encrypted. It only signifies that it contains a character which RFC2849 says must be base64-encoded. When you decode it, it may or may not be a password hash, depending on your server configuration when you loaded that value.

--
mike

References:
- Double colon in LDIF
  - From: rob fielding <rob@dsvr.net>
- Re: Double colon in LDIF
  - From: Owen DeLong <owen@delong.com>

Prev by Date: Re: db corruption?
Next by Date: syncrepl style client library functions
Index(es):
- Chronological
- Thread