[lkml]   [2007]   [May]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSMhook
    On Tuesday 29 May 2007 12:46, Tetsuo Handa wrote:
    > But, from the pathname-based access control's point of view,
    > bind mount interferes severely with pathname-based access control
    > because it is impossible to determine which pathname was requested.

    Wrong. It is very well possible to determine the path of a particular dentry
    (+ vfsmount) with bind mounts.

    > Although both pathnames point to the same object, TOMOYO focuses on the
    > PROCEDURE FOR REACHING AN OBJECT and being able to know the procedure is
    > very important.

    This doesn't make sense, either. With the following sequence of syscalls of
    processes A and B (both of them in the namespace root),

    A: B:
    rename("/tmp/a", "/tmp/b")

    the path being checked for the creat call must be "/tmp/b/f", even though
    process A never explicitly used "b". If that's not what TOMOYO is doing, then
    that's badly broken.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-05-29 19:11    [W:0.023 / U:36.508 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site