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

On Sat, 26 May 2007, Kyle Moffett wrote:

> AppArmor).  On the other hand, if you actually want to protect the _data_,
> then tagging the _name_ is flawed; tag the *DATA* instead.

Bingo.  

(This is how traditional Unix DAC has always functioned, and is what 
SELinux does: object labeling).


- James
-- 
James Morris
<[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 LSM hook
  - From: "Toshiharu Harada" <[email protected]>

References:
- Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSM hook
  - From: Casey Schaufler <[email protected]>
- Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSM hook
  - From: Kyle Moffett <[email protected]>

Prev by Date: Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSM hook
Next by Date: Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
Previous by thread: Re: Pass struct vfsmount to the inode_create LSM hook
Next by thread: Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSM hook
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]