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

Re: RFC2256: userPassword

To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
Subject: Re: RFC2256: userPassword
From: mcs@netscape.com (Mark C Smith)
Date: Wed, 30 Jun 1999 13:08:36 -0400
Cc: David Boreham <dboreham@netscape.com>, Helmut Volpers <helmut.volpers@icn.siemens.de>, " ietf-ldapext@netscape.com" <ietf-ldapext@netscape.com>
Organization: Netscape Communications
References: <199906291850.LAA14641@ego.mind.net> <37791A7F.8A03E9FF@netscape.com> <3779CB5E.983CBAC@icn.siemens.de> <377A35AA.F1638F8F@netscape.com> <377A3956.ADA1E321@icn.siemens.de> <3.0.5.32.19990630094003.009dacd0@localhost>
Resent-date: Wed, 30 Jun 1999 10:09:29 -0700 (PDT)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"dBzvbC.A.KuC.28ke3"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

"Kurt D. Zeilenga" wrote:
> ...
> I believe it wise to formalize a mechanism
> to exchange hashed password values.  I would
> suggest that such include a mechanism for client
> discovery of hash algorithms supported by the server
> and/or discovery of whether the server can and
> will perform hash generation when a cleartext
> password value is set.

I agree.  I would be willing to help author a document on this.

-- 
Mark Smith
Directory Architect / Sun-Netscape Alliance
My words are my own, not my employer's.  Got LDAP?

References:
- Re: RFC2256: userPassword
  - From: Paul Collins <paul@oneclick.com>
- Re: RFC2256: userPassword
  - From: dboreham@netscape.com (David Boreham)
- Re: RFC2256: userPassword
  - From: Helmut Volpers <helmut.volpers@icn.siemens.de>
- Re: RFC2256: userPassword
  - From: dboreham@netscape.com (David Boreham)
- Re: RFC2256: userPassword
  - From: Helmut Volpers <helmut.volpers@icn.siemens.de>
- Re: RFC2256: userPassword
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>

Prev by Date: Re: RFC2256: userPassword
Next by Date: RE: RFC2256: userPassword
Index(es):
- Chronological
- Thread