From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: David Safford <safford@watson.ibm.com>,
linux-audit@redhat.com, Reiner Sailer <sailer@us.ibm.com>
Subject: Re: [RFC][PATCH] audit: get inode pathname patch
Date: Wed, 13 Aug 2008 18:28:32 -0400 [thread overview]
Message-ID: <1218666512.2987.38.camel@localhost.localdomain> (raw)
In-Reply-To: <200808121947.59800.sgrubb@redhat.com>
On Tue, 2008-08-12 at 19:47 -0400, Steve Grubb wrote:
> On Wednesday 06 August 2008 10:36:46 Mimi Zohar wrote:
> > We are interested in using auditing's context pathname information.
> > Is this the best way of accessing it?
> >
> > Add support for accessing auditing's inode full pathname.
>
> What would this be used for? Al could you comment on this? Would there be
> locking issues?
The IMA measurement hash list contains a file name hint. Using
a full pathname, when available, would be nice.
Mimi
prev parent reply other threads:[~2008-08-13 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 14:36 [RFC][PATCH] audit: get inode pathname patch Mimi Zohar
2008-08-06 18:26 ` Serge E. Hallyn
2008-08-12 23:47 ` Steve Grubb
2008-08-13 22:28 ` 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=1218666512.2987.38.camel@localhost.localdomain \
--to=zohar@linux.vnet.ibm.com \
--cc=linux-audit@redhat.com \
--cc=safford@watson.ibm.com \
--cc=sailer@us.ibm.com \
--cc=sgrubb@redhat.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