All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janne Karhunen <janne.karhunen@gmail.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
	Chuck Lever <chuck.lever@oracle.com>,
	linux-integrity@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>
Subject: Re: IMA on remote file systems
Date: Thu, 19 Sep 2019 09:47:52 +0300	[thread overview]
Message-ID: <CAE=NcrbHLU9=6yv9XwsP6PDMcWNAp5QUML5UKhj6vjZkqN=PbQ@mail.gmail.com> (raw)
In-Reply-To: <1568821962.5817.17.camel@HansenPartnership.com>

On Wed, Sep 18, 2019 at 6:53 PM James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:

> Mutability for integrity checked executables/data is problematic.  With
> IMA you have to update the file and the xattr and make sure nothing
> touches it before you've completed all the updates otherwise you get an
> integrity check failure.  This can work if your mutation is simply a
> distro update, but it's really hard to do if the file is constantly
> undergoing mutation because the window where the integrity check fails
> is huge ... thus it depends on your use case for mutability.

Right, but try those patches I posted. They mostly address this, even
android mmap'd databases seem to stay pretty well up to date and the
performance is not entirely destroyed either if tuned a bit.


--
Janne

  reply	other threads:[~2019-09-19  6:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 17:36 IMA on remote file systems Chuck Lever
2019-09-13 14:50 ` Chuck Lever
2019-09-15 21:42   ` Mimi Zohar
2019-09-16 16:10     ` Theodore Y. Ts'o
2019-09-16 18:16       ` Chuck Lever
2019-09-16 13:16 ` Janne Karhunen
2019-09-16 14:47   ` Chuck Lever
2019-09-17  6:30     ` Janne Karhunen
2019-09-17 12:45       ` Theodore Y. Ts'o
2019-09-17 14:18         ` Mimi Zohar
2019-09-17 14:56         ` James Bottomley
2019-09-18  5:27           ` Janne Karhunen
2019-09-18 12:50             ` Theodore Y. Ts'o
2019-09-18 15:52             ` James Bottomley
2019-09-19  6:47               ` Janne Karhunen [this message]
2019-09-18 12:37           ` Theodore Y. Ts'o
2019-09-18 14:40             ` Mimi Zohar
2019-09-18 15:49             ` James Bottomley

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='CAE=NcrbHLU9=6yv9XwsP6PDMcWNAp5QUML5UKhj6vjZkqN=PbQ@mail.gmail.com' \
    --to=janne.karhunen@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=zohar@linux.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 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.