linux-kernel - Re: [PATCH v3] rootfs: Fix support for rootfstype= when root= is given

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]

Date: Thu, 4 Jan 2024 09:06:45 +0300
From: Askar Safin <safinaskar@...il.com>
To: Rob Landley <rob@...dley.net>
Cc: Stefan Berger <stefanb@...ux.ibm.com>, gregkh@...uxfoundation.org, 
	initramfs@...r.kernel.org, linux-kernel@...r.kernel.org, 
	stable@...r.kernel.org, zohar@...ux.ibm.com
Subject: Re: [PATCH v3] rootfs: Fix support for rootfstype= when root= is given

On Sat, Dec 30, 2023 at 8:01 PM Rob Landley <rob@...dley.net> wrote:
> I've been following the initramfs xattr support threads forever:

Here is my proposal: add to the kernel support for catar (
https://0pointer.net/blog/casync-a-tool-for-distributing-file-system-images.html
) in addition to cpio. catar has the following advantages:

- catar is simple and reproducible. For the same directory tree the
same bit-precise catar file is generated, which is good for
cryptographic signatures. As opposed to tar's monstrosity (
https://www.cyphar.com/blog/post/20190121-ociv2-images-i-tar )
- catar has support for xattr. It has support for nearly all types of
metainformation Linux offers (32 bit UIDs, nanosecond timestamps,
"disable CoW" flag and various other flags, selinux file labels, file
capabilities, etc). All this metainformation can be disabled if
needed. So, next time we will want to add some new type of
metainformation, there will be no need for lengthy discussions about
how it should be stored. All needed metainformation is already
supported

--
Askar Safin