Messages in this thread | | | Date | Wed, 19 Apr 2006 17:48:17 -0400 | From | Yuichi Nakamura <> | Subject | Re: [RESEND][RFC][PATCH 2/7] implementation of LSM hooks |
| |
On Wed, 19 Apr 2006 14:10:39 -0700 Crispin Cowan wrote: > Does it label the file system as well? If not, then the path names you > can specify with different access rights would be very limited. If so, > then any change to the policy requires a relabellings. Yes, files are labeled. We make diff between before modification and after modification, and relabeles only files whose label definition have changed. So it does not take much time to relabel.
> More than just sysfs. All network attached storage (NFS mounted file > systems) cannot support xattr. One could imagine supporting xattr for > Linux-based NFS servers, but that just won't work for non-linux storage > servers. I think it is correct.
> Suppose we want to write a profile for fingerd. In AppArmor, the rule > would be "/home/*/.plan r" to grant read access to everyone's .plan > file. Some people don't have a .plan file, but they do create them ad > hoc as time goes on. What does seedit do in that case? Now seedit can not resolve this by itself. One solution is to watch file creation by "restorecond". (restorecond: http://danwalsh.livejournal.com/4368.html) But we have to create list of possible file names.
--- Yuichi Nakamura - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |