[19580] in Kerberos_V5_Development
Re: krb5 commit: Modernize UTF-8/UCS-2 conversion code
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Apr 18 11:49:59 2017
To: Stefan Metzmacher <metze@samba.org>
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <ade53190-37b5-31e1-1d0e-0128e00a15d9@mit.edu>
Date: Tue, 18 Apr 2017 11:49:43 -0400
MIME-Version: 1.0
In-Reply-To: <4fc839eb-c47b-5762-6c8a-5c88e94f00e4@samba.org>
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 04/18/2017 04:32 AM, Stefan Metzmacher wrote:
> Ok, "Modernize UTF-8/UCS-2 conversion code" indicated a more or less
> rewrite of the code to me. As it's not you may just ignore this topic
> for now.
Yeah, in this case "Modernize" referred to coding standards, not
functionality. We're not always consistent about that (e.g. a recent
commit "Modernize UTF-8 conversions" was about the maximum Unicode code
point), but we can't always be perfectly clear in the summary line as we
need to keep it short.
I have written up UTF-16 support for these conversion functions, but
we'll need test cases in order to be confident that they work. Do you
or anyone else know of a body of test cases that I might crib from?
> I think Windows always supported UTF-16 instead of USC-2, at least it
> did for the last 10 years (at least for passwords).
Wikipedia thinks it added UTF-16 support in Windows 2000, so yeah, quite
some time.
> The core of the problem [...]
Thanks for that explanation.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
