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

Re: Textual/non-textual passwords and SASLprep

To: Jim Sermersheim <jimse@novell.com>
Subject: Re: Textual/non-textual passwords and SASLprep
From: Michael Ströder <michael@stroeder.com>
Date: Wed, 12 Nov 2003 17:37:42 +0100
Cc: ietf-ldapbis@OpenLDAP.org
In-reply-to: <sfb1f336.000@prv-mail20.provo.novell.com>
References: <sfb1f336.000@prv-mail20.provo.novell.com>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

Jim Sermersheim wrote:

(Lifting snippets from here and there) How does this sound? Textual passwords (consisting of a character sequence with a known character set and encoding) SHALL be transferred as [UTF-8] encoded [Unicode]. The determination of whether a password is textual is a local client matter. Prior to transfer, clients SHOULD prepare text passwords by applying the [SASLprep] profile of the [Stringprep] algorithm. Passwords consisting of other data (such as random octets) MUST NOT be altered.


Sounds ok for me.

Ciao, Michael.

References:
- Re: Textual/non-textual passwords and SASLprep
  - From: "Jim Sermersheim" <jimse@novell.com>

Prev by Date: Protocol: referrals and other URIs
Next by Date: Re: Protocol: referrals and other URIs
Index(es):
- Chronological
- Thread