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

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

Message-ID: <20171016072845.ksdtda5zdnb66mbe@pali>
Date:   Mon, 16 Oct 2017 09:28:45 +0200
From:   Pali Rohár <pali.rohar@...il.com>
To:     Andreas Bombe <aeb@...ian.org>
Cc:     Karel Zak <kzak@...hat.com>, util-linux@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Andrius Štikonas <andrius@...konas.eu>,
        Curtis Gedak <gedakc@...il.com>
Subject: Re: Linux & FAT32 label

On Monday 16 October 2017 03:12:43 Andreas Bombe wrote:
> The other thing is completely ignoring the boot sector label, which I
> could have as a mode enabled by command line switch or environmental
> variable, or just outright make it the default. I'm not decided yet.
> 
> Another problem is whether to also ignore boot sector on setting label.
> Otherwise the sequence:
>   "set label on Linux" (both root and boot)
>   "change label on Windows" (root label is changed)
>   "remove label on Windows" (root label is deleted)
>   "view label on Linux" (no root label, use boot label)
> resurrects an old label.

There is also mlabel tool which is heavily used (e.g. by gparted GUI
application) and when setting new label it stores it to both location.

And because gparted is used on Linux, such situation as described above
can still happen.

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