linux-kernel - Re: [PATCH 1/6] efi: move utf16 string functions to efi.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1365592717.3072.57.camel@shinybook.infradead.org>
Date:	Wed, 10 Apr 2013 12:18:37 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Mike Waychison <mikew@...gle.com>
Cc:	Matt Fleming <matt@...sole-pimps.org>,
	"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Matt Fleming <matt.fleming@...el.com>,
	Tom Gundersen <teg@...m.no>
Subject: Re: [PATCH 1/6] efi: move utf16 string functions to efi.h

On Tue, 2013-04-09 at 15:00 -0700, Mike Waychison wrote:
> fwiw, I was tempted to rename these to ucs2_*() last time I was here.

We should definitely do that. The functions aren't implementing UTF-16.

Note that Windows *does* now implement UTF16 I think, but EFI still
claims to be UCS2 only. 

If I interpret this correctly, the claim is basically that Windows was
"always" actually UTF16, but just never used any of the code points
where you'd be able to notice the difference:
http://blogs.msdn.com/b/michkap/archive/2005/05/11/416552.aspx

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@...el.com                              Intel Corporation




Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (6171 bytes)