From: Rob Landley <rob@landley.net>
To: Roberto Sassu <roberto.sassu@huawei.com>, viro@zeniv.linux.org.uk
Cc: linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org, initramfs@vger.kernel.org,
linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, bug-cpio@gnu.org,
zohar@linux.vnet.ibm.com, silviu.vlasceanu@huawei.com,
dmitry.kasatkin@huawei.com, takondra@cisco.com,
kamensky@cisco.com, hpa@zytor.com, arnd@arndb.de,
james.w.mcmechan@gmail.com, niveditas98@gmail.com
Subject: Re: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
Date: Mon, 3 Jun 2019 13:32:53 -0500 [thread overview]
Message-ID: <541e9ea1-024f-5c22-0b58-f8692e6c1eb1@landley.net> (raw)
In-Reply-To: <cf9d08ca-74c7-c945-5bf9-7c3495907d1e@huawei.com>
On 6/3/19 4:31 AM, Roberto Sassu wrote:
>> This patch set aims at solving the following use case: appraise files from
>> the initial ram disk. To do that, IMA checks the signature/hash from the
>> security.ima xattr. Unfortunately, this use case cannot be implemented
>> currently, as the CPIO format does not support xattrs.
>>
>> This proposal consists in including file metadata as additional files named
>> METADATA!!!, for each file added to the ram disk. The CPIO parser in the
>> kernel recognizes these special files from the file name, and calls the
>> appropriate parser to add metadata to the previously extracted file. It has
>> been proposed to use bit 17:16 of the file mode as a way to recognize files
>> with metadata, but both the kernel and the cpio tool declare the file mode
>> as unsigned short.
>
> Any opinion on this patch set?
>
> Thanks
>
> Roberto
Sorry, I've had the window open since you posted it but haven't gotten around to
it. I'll try to build it later today.
It does look interesting, and I have no objections to the basic approach. I
should be able to add support to toybox cpio over a weekend once I've got the
kernel doing it to test against.
Rob
next prev parent reply other threads:[~2019-06-03 18:31 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 12:18 [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk Roberto Sassu
2019-05-23 12:18 ` [PATCH v4 1/3] initramfs: add file metadata Roberto Sassu
2022-06-15 17:54 ` Eugeniu Rosca
2019-05-23 12:18 ` [PATCH v4 2/3] initramfs: read metadata from special file METADATA!!! Roberto Sassu
2019-07-01 12:54 ` Mimi Zohar
2019-05-23 12:18 ` [PATCH v4 3/3] gen_init_cpio: add support for file metadata Roberto Sassu
2019-06-30 15:27 ` Mimi Zohar
2022-06-16 14:47 ` Eugeniu Rosca
2022-06-16 15:16 ` Eugeniu Rosca
2022-06-30 15:06 ` Roberto Sassu
2022-06-30 20:38 ` Eugeniu Rosca
2019-06-03 9:31 ` [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk Roberto Sassu
2019-06-03 18:32 ` Rob Landley [this message]
2019-06-26 8:15 ` Roberto Sassu
2019-06-30 15:39 ` Mimi Zohar
2019-07-01 13:42 ` Roberto Sassu
2019-07-01 14:31 ` Mimi Zohar
2019-07-15 16:54 ` Roberto Sassu
2019-07-24 15:34 ` Roberto Sassu
2022-06-09 10:26 ` Eugeniu Rosca
2022-06-09 11:05 ` Roberto Sassu
2022-06-10 15:33 ` Eugeniu Rosca
2022-06-10 15:38 ` Roberto Sassu
2022-06-15 9:27 ` Eugeniu Rosca
2022-07-18 16:36 ` Jim Baxter
2022-07-18 16:49 ` Roberto Sassu
2022-07-18 18:08 ` Jim Baxter
2022-07-19 6:55 ` Roberto Sassu
2022-07-19 11:50 ` Rob Landley
2022-07-19 12:26 ` Roberto Sassu
2022-07-19 14:14 ` Rob Landley
2022-07-20 11:52 ` Roberto Sassu
2022-07-29 10:37 ` Jim Baxter
2022-07-30 9:39 ` Rob Landley
2022-07-19 11:33 ` Rob Landley
2022-07-19 11:00 ` Rob Landley
2019-07-01 13:22 ` Mimi Zohar
2022-06-15 15:50 ` Alexander Lobakin
2022-06-15 16:03 ` Roberto Sassu
2022-06-16 13:24 ` Eugeniu Rosca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=541e9ea1-024f-5c22-0b58-f8692e6c1eb1@landley.net \
--to=rob@landley.net \
--cc=arnd@arndb.de \
--cc=bug-cpio@gnu.org \
--cc=dmitry.kasatkin@huawei.com \
--cc=hpa@zytor.com \
--cc=initramfs@vger.kernel.org \
--cc=james.w.mcmechan@gmail.com \
--cc=kamensky@cisco.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=niveditas98@gmail.com \
--cc=roberto.sassu@huawei.com \
--cc=silviu.vlasceanu@huawei.com \
--cc=takondra@cisco.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zohar@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).