linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v3 0/4] unverifiable file signatures
Date: Tue, 13 Mar 2018 16:40:10 -0400	[thread overview]
Message-ID: <1520973610.3547.366.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <87zi3bwyql.fsf@xmission.com>

On Tue, 2018-03-13 at 14:40 -0500, Eric W. Biederman wrote:
> Mimi Zohar <zohar@linux.vnet.ibm.com> writes:
> 
> > For local filesystems, the kernel prevents files being executed from
> > being modified.  With IMA-measurement enabled, the kernel also emits
> > audit "time of measure, time of use" messages for files opened for
> > read, and subsequently opened for write.
> >
> > Files on fuse are initially measured, appraised, and audited.  Although
> > the file data can change dynamically any time, making re-measuring,
> > re-appraising, or re-auditing pointless, this patch set attempts to
> > differentiate between unprivileged non-init root and privileged
> > mounted fuse filesystems.
> 
> Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
> 
> Overall ack on the way this is put together.

Thanks you!

Mimi

--
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

      reply	other threads:[~2018-03-13 20:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 20:24 [PATCH v3 0/4] unverifiable file signatures Mimi Zohar
2018-03-08 20:24 ` [PATCH v3 1/4] ima: fail file signature verification on non-init mounted filesystems Mimi Zohar
2018-03-12 19:17   ` Serge E. Hallyn
2018-03-12 19:26     ` Serge E. Hallyn
2018-03-13 18:45   ` Eric W. Biederman
2018-03-08 20:24 ` [PATCH v3 2/4] ima: re-evaluate files on privileged " Mimi Zohar
2018-03-12 19:18   ` Serge E. Hallyn
2018-03-13 19:24   ` Eric W. Biederman
2018-03-08 20:24 ` [PATCH v3 3/4] ima: fail signature verification based on policy Mimi Zohar
2018-03-12 19:28   ` Serge E. Hallyn
2018-03-12 19:32     ` Mimi Zohar
2018-03-13 19:31   ` Eric W. Biederman
2018-03-08 20:24 ` [PATCH v3 4/4] fuse: define the filesystem as untrusted Mimi Zohar
2018-03-12 19:29   ` Serge E. Hallyn
2018-03-13 14:46     ` Stefan Berger
2018-03-14 14:27       ` Serge E. Hallyn
2018-03-14 14:37         ` Stefan Berger
2018-03-13 19:32   ` Eric W. Biederman
2018-03-19 11:57     ` Mimi Zohar
2018-03-14  7:52   ` Stef Bon
2018-03-14 13:01     ` Mimi Zohar
2018-03-14 16:17       ` Eric W. Biederman
2018-03-14 17:50         ` Mimi Zohar
2018-03-14 18:08           ` Chuck Lever
2018-03-14 19:46             ` Eric W. Biederman
2018-03-14 20:34               ` Chuck Lever
2018-03-14 21:42                 ` Eric W. Biederman
2018-03-14 22:53                   ` Michael Halcrow
2018-03-15 21:24                     ` Mimi Zohar
2018-03-15 10:07                   ` Stef Bon
2018-03-15 13:53                     ` Chuck Lever
2018-03-15 22:05               ` Mimi Zohar
2018-03-13 19:40 ` [PATCH v3 0/4] unverifiable file signatures Eric W. Biederman
2018-03-13 20:40   ` Mimi Zohar [this message]

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=1520973610.3547.366.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=linux-security-module@vger.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 NNTP newsgroup(s).