Re: Determing the difference between path_walk and chdir ?

Previous message: jmjonesat_private: "Re: GPL only usage of security.h"
In reply to: richard offer: "Determing the difference between path_walk and chdir ?"
Next in thread: richard offer: "Re: Determing the difference between path_walk and chdir ?"
Reply: richard offer: "Re: Determing the difference between path_walk and chdir ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

chrisat_private

* richard offer (offerat_private) wrote:
> 
> 
> Has anyone any ideas on how to tell the difference between walking the path
> (which calls permission(MAY_EXEC)) and chdir (which calls
> permission(MAY_EXEC)) ? Generating bogus chdir events for every path walk
> seems sub-optimal.

hmm, the chdir case doesn't really seem any different to me than the
path walk case ;-)

> I was thinking about proposing a new hook in set_fs_pwd and friends, but my
> proposals haven't met with much success :-)

set_fs_[pwd,root,altroot] do fall within the scope of the current
hooking paradigm as task_ops hooks, but i sure don't like imposing a
double check in the code path like that.

-chris

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