Re: Determing the difference between path_walk and chdir ?

Previous message: Crispin Cowan: "Re: Binary only module overview"
In reply to: David Wagner: "Re: Determing the difference between path_walk and chdir ?"
Next in thread: Valdis.Kletnieksat_private: "Re: Determing the difference between path_walk and chdir ?"
Next in thread: Stephen Smalley: "Re: Determing the difference between path_walk and chdir ?"
Reply: Valdis.Kletnieksat_private: "Re: Determing the difference between path_walk and chdir ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

offerat_private

* frm dawat_private "09/26/01 01:40:02 +0000" | sed '1,$s/^/*
/'
*
* richard offer  wrote:
*> I don't want to keep shadow state to emulate what the kernel is doing, I
*> just want to record the directory/file that has been passed to
*> sys_chdir() for audit.
* 
* Ahh, ok.  I guess a number of folks have suggested that changes to LSM
* made solely to support audit should be deferred, so maybe we should put
* off this question for a bit.

I've been hit over the head enough times now that I'm not even going there
:-)

Not to get defensive, but I didn't say anything about adding code for
audit, I just wanted to see if anyone had worked around the same issue and
if so, what subtle logic was I missing.

richard.

-----------------------------------------------------------------------
Richard Offer                     Technical Lead, Trust Technology, SGI
"Specialization is for insects"
_______________________________________________________________________

_______________________________________________
linux-security-module mailing list
linux-security-moduleat_private
http://mail.wirex.com/mailman/listinfo/linux-security-module