linux-kernel - Re: vfat: Broken case-insensitive support for UTF-8

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20200121110049.4upreexmv5kxwp5n@pali>
Date:   Tue, 21 Jan 2020 12:00:49 +0100
From:   Pali Rohár <pali.rohar@...il.com>
To:     OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
Cc:     "Theodore Y. Ts'o" <tytso@....edu>, linux-kernel@...r.kernel.org,
        linux-fsdevel@...r.kernel.org, Namjae Jeon <linkinjeon@...il.com>,
        Gabriel Krisman Bertazi <krisman@...labora.com>
Subject: Re: vfat: Broken case-insensitive support for UTF-8

On Tuesday 21 January 2020 12:52:50 OGAWA Hirofumi wrote:
> BTW, VFAT has to store the both of shortname (codepage) and longname
> (UTF16), and using both names to open a file. So Windows should be using
> current locale codepage to make shortname even latest Windows for VFAT.

fastfat.sys stores into shortnames only 7bit characters. Which is same
in all OEM codepages. Non-7bit are replaced by underline or shortened by
"~N" syntax. According to source code of fastfat.sys it has some
registry option to allow usage also of full 8bit OEM codepage.

So default behavior seems to be safe.

-- 
Pali Rohár
pali.rohar@...il.com