From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mimi Zohar Subject: Re: [RFC][PATCH] audit: get inode pathname patch Date: Wed, 13 Aug 2008 18:28:32 -0400 Message-ID: <1218666512.2987.38.camel@localhost.localdomain> References: <1218033406.9023.7.camel@new-host-2.home> <200808121947.59800.sgrubb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200808121947.59800.sgrubb@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Steve Grubb Cc: David Safford , linux-audit@redhat.com, Reiner Sailer List-Id: linux-audit@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