login
Header Space

 
 

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

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <Valdis.Kletnieks@...>
Cc: Kyle Moffett <mrmacman_g4@...>, Toshiharu Harada <haradats@...>, James Morris <jmorris@...>, <casey@...>, Andreas Gruenbacher <agruen@...>, <linux-kernel@...>, <linux-security-module@...>, <linux-fsdevel@...>
Date: Wednesday, May 30, 2007 - 1:52 am

Valdis.Kletnieks@vt.edu wrote:
That explains so much! "SELinux: you're too dumb to use it, so just keep
your hands in your pockets." :-)

AppArmor was designed to allow your average sys admin to write a
security policy. It makes different design choices than SELinux to
achieve that goal. As a result, AppArmor is an utter failure when
compared to SELinux's goals, and SELinux in turn is an utter failure
when compared to AppArmor's goals.

Which is why we have LSM: so we don't have to have this argument here,
again.

That is a tall order. You can mostly achieve it by not giving the user
the root password, but I'm not sure you would like the result :-)

Both SELinux and AppArmor can be configured so tightly that you are not
going to get to install malware, by preventing the user from installing
software. This isn't what users want, so they invariably bypass security
and install shiny things if they own the box. SELinux and AppArmor can't
help but fail if you put them in that kind of harm's way.

Crispin

-- 
Crispin Cowan, Ph.D.               http://crispincowan.com/~crispin/
Director of Software Engineering   http://novell.com
		   Security: It's not linear

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Andreas Gruenbacher, (Thu May 24, 2:10 pm)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Toshiharu Harada, (Tue May 29, 10:38 pm)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Crispin Cowan, (Wed May 30, 1:52 am)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Andreas Gruenbacher, (Sat May 26, 7:46 am)
Re: Pass struct vfsmount to the inode_create LSM hook, Tetsuo Handa, (Sat May 26, 8:09 am)
Re: Pass struct vfsmount to the inode_create LSM hook, Andreas Gruenbacher, (Sat May 26, 9:41 am)
Re: Pass struct vfsmount to the inode_create LSM hook, Tetsuo Handa, (Sat May 26, 10:44 am)
Re: Pass struct vfsmount to the inode_create LSM hook, Kyle Moffett, (Sat May 26, 2:16 pm)
Re: Pass struct vfsmount to the inode_create LSM hook, Andreas Gruenbacher, (Sat May 26, 12:52 pm)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Jeremy Maitin-Shepard, (Fri May 25, 1:17 am)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Andreas Gruenbacher, (Fri May 25, 4:00 pm)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Andreas Gruenbacher, (Sat May 26, 10:05 am)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Jeremy Maitin-Shepard, (Fri May 25, 2:10 pm)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Andreas Gruenbacher, (Sat May 26, 8:10 am)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Jeremy Maitin-Shepard, (Fri May 25, 2:13 pm)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Andreas Gruenbacher, (Fri May 25, 12:14 am)
Re: [AppArmor 01/41] Pass struct vfsmount to the inode_creat..., Andreas Gruenbacher, (Thu May 24, 5:56 pm)
speck-geostationary