linux-kernel - vfat file system does not allow a space at the end of a directory name

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-next>] [day] [month] [year] [list]

Date:   Sun, 30 Jul 2023 23:33:03 +0100
From:   Chris Ward <tjcw01@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: vfat file system does not allow a space at the end of a directory name

I had a zip file (from downloading pictures from Google Photos) where
some of the directory names had a space at the end. This unzipped fine
on an ext4 file system, but gave errors when unpacking onto a USB key
which had a FAT file system.

On further investigation, file names have the same problem. On my USB key, I get

tjcw@...w-OptiPlex-7010:/media/tjcw/Photos$ touch 'aab '
touch: setting times of 'aab ': No such file or directory
tjcw@...w-OptiPlex-7010:/media/tjcw/Photos$ echo ok >'aab '
bash: aab : Invalid argument
tjcw@...w-OptiPlex-7010:/media/tjcw/Photos$ touch 'aab'
tjcw@...w-OptiPlex-7010:/media/tjcw/Photos$ echo ok >'aab'
tjcw@...w-OptiPlex-7010:/media/tjcw/Photos$

Is this as expected, or is it a bug in the kernel's handling of FAT
file systems ? Probably the next step is to check the behaviour under
Microsoft Windows.

Chris Ward