Re: [ldapext] draft-stroeder-hashed-userpassword-values-01

[Michael Ströder <[e-mail]>]

Andrew Findlay wrote:
> On Wed, Mar 13, 2013 at 11:39:28PM +0100, Michael Ströder wrote:
> 
>>> I see this document is marked as being intended to be published as
>>> Informational, but it reads more like it's trying to be a standard.
>>
>> I tried to add some wording to avoid that misunderstanding in the next
>> revision of this draft:
>>
>> http://www.ietf.org/internet-drafts/draft-stroeder-hashed-userpassword-values-01.txt
> 
> Still -01 ?

Not "still" -01. Now -01.

> You are explicitly excluding details of '{crypt}'. I think this is a
> mistake, especially in an informational document. {crypt} is
> extremely useful in transition scenarios, so people need to know about
> it.

Hmm...I've expected somebody to ask for it. :-/
It makes the spec part more complex.

> What platform-specific variants do you know of?

Well, looking at crypt(3) man page it seems to me that there are many variants
of the library on various Unix platforms. This is what I meant with
"platform-specific".

> The really important one is the old Unix-crypt 13-char salted hash.
> 
> Could you perhaps say something like:
> 
> {crypt} introduces a password-hash string that is generated and
> checked by the crypt(3) library. This could be the traditional
> 13-character 'Unix crypt' or some other variant such as the stronger
> '$1$' and $6$' schemes used by recent versions of Linux.

I've added some text hopefully getting {CRYPT} stuff complete. Yuck!

Ciao, Michael.