All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/2] evm: disable EVM on overlayfs
Date: Tue, 19 Dec 2023 08:48:59 -0500	[thread overview]
Message-ID: <20231219134901.96300-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.

Mimi Zohar (2):
  evm: don't copy up 'security.evm' xattr
  evm: add support to disable EVM on unsupported filesystems

 include/linux/evm.h               |  6 +++++
 security/integrity/evm/evm_main.c | 42 ++++++++++++++++++++++++++++++-
 security/security.c               |  4 +++
 3 files changed, 51 insertions(+), 1 deletion(-)

-- 
2.39.3


             reply	other threads:[~2023-12-19 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 13:48 Mimi Zohar [this message]
2023-12-19 13:49 ` [PATCH 1/2] evm: don't copy up 'security.evm' xattr Mimi Zohar
2023-12-19 14:41   ` Amir Goldstein
2023-12-19 13:49 ` [PATCH 2/2] evm: add support to disable EVM on unsupported filesystems Mimi Zohar
2023-12-19 14:47   ` Amir Goldstein

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=20231219134901.96300-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 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.