From: Dave Chinner <david@fromorbit.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: rishi gupta <gupt21@gmail.com>,
zohar@linux.vnet.ibm.com, dmitry.kasatkin@gmail.com,
linux-integrity@vger.kernel.org,
"Theodore Y. Ts'o" <tytso@mit.edu>
Subject: Re: ima: why IMA_APPRAISE_DIRECTORIES patch is not mainlined
Date: Fri, 6 Jul 2018 08:56:51 +1000 [thread overview]
Message-ID: <20180705225650.GV19934@dastard> (raw)
In-Reply-To: <1530803798.3773.112.camel@linux.ibm.com>
On Thu, Jul 05, 2018 at 11:16:38AM -0400, Mimi Zohar wrote:
> [CC'ing Dave Chinner, Ted Tso]
>
> Hi Rishi,
>
> On Thu, 2018-07-05 at 16:08 +0530, rishi gupta wrote:
> > Hi Dmitry and security team members,
> >
> > I am willing to take directory protection ima patch in a commercial
> > product, but observed that it has not been mainlined. Is there any reason
> > for not mainlining it. Are there any better options for protecting
> > directory using IMA/EVM or some other security schemes.
> >
> > https://lwn.net/Articles/512364/
> > https://kernel.googlesource.com/pub/scm/linux/kernel/git/kasatkin/linux-digsig/+/ima-dir-experimental/security/integrity/ima/ima_dir.c
>
> The main purpose of the IMA-directory patch set is to protect file
> names from offline attack. Dmitry's patch set protects file names at
> the immediate directory level, but does not extend up to the root
> directory. I brought up the topic of protecting file names at
> LSF/MM[1]. Others in the community are aware of the problem and need
> to be involved in the discussions as to how to address it.
Probably best to take any discussion to the -fsdevel list. Verifying
directories are unchanged doesn't guarantee that access to
individual files is unchanged, though. Hardlinks can be made
from outside the verified directory and symlinks can cross
filesystem boundaries from outside verified filesystems...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2018-07-05 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALUj-gtOL3wDoo=QC68zhnwOsnfBistA_X97WzWAu6_v5T-xWQ@mail.gmail.com>
2018-07-05 15:16 ` ima: why IMA_APPRAISE_DIRECTORIES patch is not mainlined Mimi Zohar
2018-07-05 22:56 ` Dave Chinner [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=20180705225650.GV19934@dastard \
--to=david@fromorbit.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=gupt21@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=zohar@linux.ibm.com \
--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