From: Christian Brauner <brauner@kernel.org>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-unionfs@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org, Amir Goldstein <amir73il@gmail.com>,
Seth Forshee <sforshee@kernel.org>,
Roberto Sassu <roberto.sassu@huaweicloud.com>
Subject: Re: [PATCH v2 0/3] evm: disable EVM on overlayfs
Date: Wed, 20 Dec 2023 13:35:40 +0100 [thread overview]
Message-ID: <20231220-komprimieren-kooperativ-cdb5e8803ce0@brauner> (raw)
In-Reply-To: <20231219175206.12342-1-zohar@linux.ibm.com>
On Tue, Dec 19, 2023 at 12:52:03PM -0500, Mimi Zohar wrote:
> EVM verifies the existing 'security.evm' value, before allowing it
> to be updated. The EVM HMAC and the original file signatures contain
> filesystem specific metadata (e.g. i_ino, i_generation and s_uuid).
>
> This poses a challenge when transitioning from the lower backing file
> to the upper backing file.
>
> Until a complete solution is developed, disable EVM on overlayfs.
>
> Changelog v2:
> Addressed Amir's comments:
> - Simplified security_inode_copy_up_xattr() return.
> - Identified filesystems that don't support EVM based on a new SB_I flag.
We're wasting a flag for a single filesystem but we do have enough of
them left so I think this is ok,
Reviewed-by: Christian Brauner <brauner@kernel.org>
next prev parent reply other threads:[~2023-12-20 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 17:52 [PATCH v2 0/3] evm: disable EVM on overlayfs Mimi Zohar
2023-12-19 17:52 ` [PATCH v2 1/3] evm: don't copy up 'security.evm' xattr Mimi Zohar
2023-12-19 17:52 ` [PATCH v2 2/3] evm: add support to disable EVM on unsupported filesystems Mimi Zohar
2023-12-19 19:09 ` Mimi Zohar
2023-12-20 4:23 ` Amir Goldstein
2023-12-19 17:52 ` [PATCH v2 3/3] overlay: disable EVM Mimi Zohar
2023-12-20 4:21 ` Amir Goldstein
2023-12-20 12:35 ` Christian Brauner [this message]
2023-12-20 14:19 ` [PATCH v2 0/3] evm: disable EVM on overlayfs Mimi Zohar
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=20231220-komprimieren-kooperativ-cdb5e8803ce0@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=roberto.sassu@huaweicloud.com \
--cc=sforshee@kernel.org \
--cc=zohar@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.