diff for duplicates of <1501601904.9230.147.camel@linux.vnet.ibm.com> diff --git a/a/1.txt b/N1/1.txt index f218a3c..81b9af8 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -10,7 +10,7 @@ On Tue, 2017-08-01 at 12:42 +0200, Jan Kara wrote: > > > > > > The patch looks mostly good to me. > > -> > Thanks! ?Can I include your Ack-by? +> > Thanks! Can I include your Ack-by? > > After gfs2 & ocfs2 matters are settled... > @@ -20,7 +20,7 @@ On Tue, 2017-08-01 at 12:42 +0200, Jan Kara wrote: > > > > Initially I started out looking at the fs/.../Kconfig, but after > > spending a while looking at the number of filesystems, I gave up and -> > asked Christoph (offline) where to begin.??I also compared the +> > asked Christoph (offline) where to begin. I also compared the > > measurement list from before and after the change and noticed some > > missing file measurements (eg. ramfs, shmem, efivarfs). > @@ -31,7 +31,7 @@ On Tue, 2017-08-01 at 12:42 +0200, Jan Kara wrote: > > > unless you either make sure they are mounted in local-only mode or figure > > > out how to deal with proper cluster locking. > > -> > Agreed. ?With patch 1/7 "ima: always measure and audit files in +> > Agreed. With patch 1/7 "ima: always measure and audit files in > > policy", at least a file measurement containing a 0x00's hash value > > will be included in the IMA measurement list. > @@ -42,12 +42,12 @@ On Tue, 2017-08-01 at 12:42 +0200, Jan Kara wrote: > suggestion is to just not provide .integrity_read for these two filesystems > until you (or someone else) can figure out how to do that safely. -Sorry my explanation above wasn't clear. ?Yes, I'll remove the -integrity_read method definitions for gfs2 and ocfs2. ?As a result of +Sorry my explanation above wasn't clear. Yes, I'll remove the +integrity_read method definitions for gfs2 and ocfs2. As a result of removing the integrity_read operation, the measurement list will contain 0x00 hash values, instead of the real file hash. -Mimi? +Mimi > @@ -516,9 +516,4 @@ Mimi? > > > > 2.7.4 > > > > > > > > -> > - --- -To unsubscribe from this list: send the line "unsubscribe linux-security-module" in -the body of a message to majordomo at vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html +> > diff --git a/a/content_digest b/N1/content_digest index 0f8e869..2f39378 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,10 +3,33 @@ "ref\020170731070151.GA18621@quack2.suse.cz\0" "ref\01501528133.9230.123.camel@linux.vnet.ibm.com\0" "ref\020170801104253.GF4215@quack2.suse.cz\0" - "From\0zohar@linux.vnet.ibm.com (Mimi Zohar)\0" - "Subject\0[PATCH v4 2/5] ima: use fs method to read integrity data\0" + "From\0Mimi Zohar <zohar@linux.vnet.ibm.com>\0" + "Subject\0Re: [PATCH v4 2/5] ima: use fs method to read integrity data\0" "Date\0Tue, 01 Aug 2017 11:38:24 -0400\0" - "To\0linux-security-module@vger.kernel.org\0" + "To\0Jan Kara <jack@suse.cz>\0" + "Cc\0Christoph Hellwig <hch@lst.de>" + Al Viro <viro@zeniv.linux.org.uk> + James Morris <jmorris@namei.org> + linux-fsdevel@vger.kernel.org + linux-ima-devel@lists.sourceforge.net + linux-security-module@vger.kernel.org + Matthew Garrett <matthew.garrett@nebula.com> + Jan Kara <jack@suse.com> + Theodore Ts'o <tytso@mit.edu> + Andreas Dilger <adilger.kernel@dilger.ca> + Jaegeuk Kim <jaegeuk@kernel.org> + Chao Yu <yuchao0@huawei.com> + Steven Whitehouse <swhiteho@redhat.com> + Bob Peterson <rpeterso@redhat.com> + David Woodhouse <dwmw2@infradead.org> + Dave Kleikamp <shaggy@kernel.org> + Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> + Mark Fasheh <mfasheh@versity.com> + Joel Becker <jlbec@evilplan.org> + Richard Weinberger <richard@nod.at> + Darrick J. Wong <darrick.wong@oracle.com> + Hugh Dickins <hughd@google.com> + " Chris Mason <clm@fb.com>\0" "\00:1\0" "b\0" "On Tue, 2017-08-01 at 12:42 +0200, Jan Kara wrote:\n" @@ -21,7 +44,7 @@ "> > > \n" "> > > The patch looks mostly good to me.\n" "> > \n" - "> > Thanks! ?Can I include your Ack-by?\n" + "> > Thanks! \302\240Can I include your Ack-by?\n" "> \n" "> After gfs2 & ocfs2 matters are settled...\n" "> \n" @@ -31,7 +54,7 @@ "> > \n" "> > Initially I started out looking at the fs/.../Kconfig, but after\n" "> > spending a while looking at the number of filesystems, I gave up and\n" - "> > asked Christoph (offline) where to begin.??I also compared the\n" + "> > asked Christoph (offline) where to begin.\302\240\302\240I also compared the\n" "> > measurement list from before and after the change and noticed some\n" "> > missing file measurements (eg. ramfs, shmem, efivarfs).\n" "> \n" @@ -42,7 +65,7 @@ "> > > unless you either make sure they are mounted in local-only mode or figure\n" "> > > out how to deal with proper cluster locking.\n" "> > \n" - "> > Agreed. ?With patch 1/7 \"ima: always measure and audit files in\n" + "> > Agreed. \302\240With patch 1/7 \"ima: always measure and audit files in\n" "> > policy\", at least a file measurement containing a 0x00's hash value\n" "> > will be included in the IMA measurement list.\n" "> \n" @@ -53,12 +76,12 @@ "> suggestion is to just not provide .integrity_read for these two filesystems\n" "> until you (or someone else) can figure out how to do that safely.\n" "\n" - "Sorry my explanation above wasn't clear. ?Yes, I'll remove the\n" - "integrity_read method definitions for gfs2 and ocfs2. ?As a result of\n" + "Sorry my explanation above wasn't clear. \302\240Yes, I'll remove the\n" + "integrity_read method definitions for gfs2 and ocfs2. \302\240As a result of\n" "removing the integrity_read operation, the measurement list will\n" "contain 0x00 hash values, instead of the real file hash.\n" "\n" - "Mimi?\n" + "Mimi\302\240\n" "\n" "\n" "> \n" @@ -527,11 +550,6 @@ "> > > > 2.7.4\n" "> > > > \n" "> > > > \n" - "> > \n" - "\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-security-module\" in\n" - "the body of a message to majordomo at vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + > > -768fe6993d0113364229a28a42982c6e08595f8a70deaf7d5e883980d570a37a +02b2f0534ad8ff9e8c2dc0a16f8287159b76e8dcc9e7bd572d347d2bdad5ca98
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.