From: Ignaz Forster <iforster@suse.de>
To: miklos@szeredi.hu, linux-unionfs@vger.kernel.org,
zohar@linux.vnet.ibm.com, linux-integrity@vger.kernel.org
Subject: PROBLEM: IMA xattrs not written on overlayfs
Date: Fri, 7 Sep 2018 18:49:32 +0200 [thread overview]
Message-ID: <81a0a75d-bd4e-25ef-b41b-adb65ac6dee8@suse.de> (raw)
Hi,
I'm currently experimenting with IMA / EVM on overlayfs, however those
don't seem to work together very well.
With kernel 4.18 it was possible to at least partially use IMA. As long
as the O_TRUNC attribute was not set during a copy_up operation
everything seemed to work so far.
Now when applying the changes from
https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git/tag/?h=ovl-update-4.19
(or using kernel 4.19-rc2) every file contents modification or creation
of a new file will fail, probably because the inode reported by
overlayfs does not match the physical inode number any more (and thus
the IMA hashes won't be generated).
A small example for reproduction (on a system with IMA appraisal):
# OVERLAYFS_TEST_DIR=`mktemp -d`
# mkdir "${OVERLAYFS_TEST_DIR}/upper"
# mkdir "${OVERLAYFS_TEST_DIR}/work"
# mount -t overlay -o lowerdir=/etc,upperdir="${OVERLAYFS_TEST_DIR}
/upper",workdir="${OVERLAYFS_TEST_DIR}/work" overlay /etc
#
# rm -f /etc/test.txt
# echo Test > /etc/test.txt
# cat /etc/test.txt
cat: /etc/test.txt: Permission denied
# ls -s /etc/test.txt
4 /etc/test.txt # <- The contents are there
# getfattr -m . -d /etc/test.txt
# # <- The hash isn't
After some debugging I'm not sure on how to continue from here. My
assumption is that overlayfs will have to be modified, however I fail to
see where to start.
Ignaz
next reply other threads:[~2018-09-07 21:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 16:49 Ignaz Forster [this message]
2018-09-07 18:45 ` PROBLEM: IMA xattrs not written on overlayfs Mimi Zohar
2018-09-10 9:17 ` Ignaz Forster
2018-09-28 16:54 ` Mimi Zohar
2018-09-28 18:24 ` Ignaz Forster
2018-09-28 19:06 ` Mimi Zohar
2018-09-28 19:37 ` Fabian Vogt
2018-10-01 9:05 ` Miklos Szeredi
2018-10-03 21:18 ` Mimi Zohar
2018-10-03 22:35 ` Miklos Szeredi
2018-10-04 15:52 ` Mimi Zohar
2018-10-05 2:57 ` Goldwyn Rodrigues
2018-10-05 10:33 ` Mimi Zohar
2018-10-05 17:30 ` Goldwyn Rodrigues
2018-10-07 8:22 ` Amir Goldstein
2018-10-08 12:54 ` 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=81a0a75d-bd4e-25ef-b41b-adb65ac6dee8@suse.de \
--to=iforster@suse.de \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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).