From: Mimi Zohar <zohar@linux.ibm.com>
To: linux-unionfs@vger.kernel.org
Cc: Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
Amir Goldstein <amir73il@gmail.com>,
Christian Brauner <brauner@kernel.org>,
Seth Forshee <sforshee@kernel.org>,
Roberto Sassu <roberto.sassu@huaweicloud.com>
Subject: [PATCH v2 0/3] evm: disable EVM on overlayfs
Date: Tue, 19 Dec 2023 12:52:03 -0500 [thread overview]
Message-ID: <20231219175206.12342-1-zohar@linux.ibm.com> (raw)
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.
Mimi Zohar (3):
evm: don't copy up 'security.evm' xattr
evm: add support to disable EVM on unsupported filesystems
overlay: disable EVM
fs/overlayfs/super.c | 1 +
include/linux/evm.h | 6 +++++
include/linux/fs.h | 1 +
security/integrity/evm/evm_main.c | 42 ++++++++++++++++++++++++++++++-
security/security.c | 2 +-
5 files changed, 50 insertions(+), 2 deletions(-)
--
2.39.3
next reply other threads:[~2023-12-19 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 17:52 Mimi Zohar [this message]
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 ` [PATCH v2 0/3] evm: disable EVM on overlayfs Christian Brauner
2023-12-20 14:19 ` 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=20231219175206.12342-1-zohar@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--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 \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).