linux-kernel - Re: Linux & FAT32 label

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]

Date:   Thu, 9 Nov 2017 18:33:43 +0100
From:   Pali Rohár <pali.rohar@...il.com>
To:     Theodore Ts'o <tytso@....edu>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Andreas Bombe <aeb@...ian.org>, Karel Zak <kzak@...hat.com>,
        util-linux@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Andrius Štikonas <andrius@...konas.eu>,
        Curtis Gedak <gedakc@...il.com>, pavel@....cz
Subject: Re: Linux & FAT32 label

On Thursday 09 November 2017 11:21:25 Theodore Ts'o wrote:
> On Thu, Nov 09, 2017 at 10:01:45AM +0100, Pali Rohár wrote:
> > > > You would have stored LABEL42 in boot sector and no label in root
> > > > directory. Windows handle this situation as there is no label.
> > > 
> > > But why should we *care*?
> > 
> > FAT is Microsoft's filesystem and the only usage of it on Linux is due
> > to interoperability with different non-Linux systems. So here we should
> > implement FAT in the similar/same way as other systems. It does not make
> > sense to implement it differently and specially in non-compatible way.
> > Because it lost reason what is primary usage of the FAT on Linux.
> 
> The primary usage of FAT on Linux is for data interchange, primarily
> with USB sticks.  I'm still failing to see how it might "spoil some
> vast eternal plan"[1] if a USB stick which Windows would show as
> having no label, blkid/udev showed as having the label "LABEL42"?
> 
> [1] to quote the song "If I were a rich man"
> 
> I'm just trying to understand why this specific detail of bit-for-bit
> compatibility is so important.

Then you can ask question: Why we are serving LABEL information to
users?

Some users really use LABEL as identifier for themself, what is either
stored on filesystem (in this case USB stick). And if somebody for some
reason want to remove label (just because it does not contain data which
label describe anymore), then user probably really want to use this
information.

LABEL is human readable identifier of particular filesystem on disk. If
one system show one label and another system show another different
label for same disk, then such information is useless.

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