Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSMhook

--- Tetsuo Handa <[email protected]> wrote:


> Conventional UNIX's access control can't restrict
> which path_to_file can link with which another_path_to_file
> because UNIX's access control is a label-based access control.

UNIX access control is attribute based, not label based. The
distinction may be hair splitting in the current context, but
could be significant later if the thread continues. 




Casey Schaufler
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSMhook
    • From: James Morris <[email protected]>

• References:
  • Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSMhook
    • From: Tetsuo Handa <[email protected]>

• Prev by Date: [PATCH] add procfs tunable to enable immediate panic when there are busy inodes after umount
• Next by Date: Re: Seeding /dev/random not working
• Previous by thread: Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSMhook
• Next by thread: Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSMhook
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]