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
| ||
|
Date: Tue, 21 Jan 2020 21:36:25 +0000 From: Al Viro <viro@...iv.linux.org.uk> To: Pali Rohár <pali.rohar@...il.com> Cc: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, "Theodore Y. Ts'o" <tytso@....edu>, Namjae Jeon <linkinjeon@...il.com>, Gabriel Krisman Bertazi <krisman@...labora.com> Subject: Re: vfat: Broken case-insensitive support for UTF-8 On Tue, Jan 21, 2020 at 09:34:05PM +0100, Pali Rohár wrote: > This is a great idea to get FAT equivalence classes. Thank you! > > Now I quickly tried it... and it failed. FAT has restriction for number > of files in a directory, so I would have to do it in more clever way, > e.g prepare N directories and then try to create/open file for each > single-point string in every directory until it success or fail in every > one. IIRC, the limitation in root directory was much harder than in subdirectories... Not sure, though - it had been a long time since I had to touch *FAT for any reasons...
Powered by blists - more mailing lists