Re: Schema: encrypted 8-bit userPassword and SASLprep

[Hallvard B Furuseth <h.b.furuseth@usit.uio.no>]

Kurt D. Zeilenga writes:
>At 04:09 AM 9/12/2003, Hallvard B Furuseth wrote:
>>[Schema] 2.41 (userPassword) says:
>>
>>   The application SHOULD prepare textual strings used as passwords
>>   by transcoding them to Unicode, applying SASLprep [SASLprep], and
>>   encoding as UTF-8.
> 
> s/application/client/
> 
> The intent here was to recommend that clients prepare textual
> passwords before storing them or using them (to improve
> interoperability).

Huh?  If clients do that but servers don't, the passwords won't match.

> Note that it is not a mandate.  It is a recommendation.

Sure, but if implementations follow that recommendation, sites with
servers using Unix /etc/passwd passwords are in trouble.  Unless they
also follow a recommendation to allow this to be turned off.

It applies to Windows servers too, I think - though passwords there are
apparently so easy to break that servers almost could do it during the
bind operation:-(

-- 
Hallvard