Linked by Thom Holwerda on Wed 26th Sep 2007 19:23 UTC
Privacy, Security, Encryption KernelTrap offers a summary of a lengthy debate on OpenBSD's -misc mailing list comparing the security features built into OpenBSD versus the security offered by the Linux kernel's SELinux feature. The main arguments presented against SELinux centered around its complexity and the difficulty of defining a secure policy. "The first thing people usually do with SELinux is turn it off", suggests the article, noting that the ease with which it can be turned off is another security shortcoming. By contrast, OpenBSD offers numerous security features that are always enabled with minimal overhead, including propolice stack protection, random library mappings, proactive privilege separation, W^X, and systrace.
Thread beginning with comment 274658
To read all comments associated with this story, please click here.
What about appamor?
by newbee on Wed 26th Sep 2007 21:25 UTC
newbee
Member since:
2007-04-21

I think everyone is looking at this all wrong.
SELinux is too hard, but the security framework itself is very good.

I'm still amazed that SUSE is the only distribution to include Apparmor http://www.novell.com/linux/security/apparmor/

It is also "open source" and uses the linux security framework and is MUCH MUCH MUCH more easy to use.

Darren

RE: What about appamor?
by superman on Wed 26th Sep 2007 22:32 in reply to "What about appamor?"
superman Member since:
2006-08-01

> and is MUCH MUCH MUCH more easy to use.

I really don't care.
I use Fedora, SeLinux is enabled and I don't touch SeLinux policy. My OS should be secure, I don't have to make it secure.
If i manually install a program and it trigger SeLinux policy, then I remove this program because this program should have security flaw. Period.
This only appened one time. Many many many programs work out of the box with SeLinux enabled. Some not but they are a very few number.

Reply Parent Bookmark Score: 3

RE: What about appamor?
by dagw on Wed 26th Sep 2007 22:34 in reply to "What about appamor?"
dagw Member since:
2005-07-06

While I agree that Apparmor is easy to to use and configure, there are a number of (in my opinion valid) critisisms leveled against it. On the whole it is not as solid a sollution as SELinux.

Personally I don't currently need the sort of security that SELinux offers, and as such I'm quite happy doing things the 'old' way (I run OpenBSD and Debian on a couple of servers). However if I needed the type of features SELinux offered then I would take the time to learn SELinux and do it right. AppArmor seems to fill some kind of in between niche that no one really needs.

Reply Parent Bookmark Score: 1

RE: What about appamor?
by leech on Wed 26th Sep 2007 23:21 in reply to "What about appamor?"
leech Member since:
2006-01-10

Apparently Ubuntu's next release, Gutsy Gibbon, is going to use Apparmor as well.

Reply Parent Bookmark Score: 1

RE: What about appamor?
by ozonehole on Thu 27th Sep 2007 00:10 in reply to "What about appamor?"
ozonehole Member since:
2006-01-07

It's my understanding that apparmor is going to be implemented in the upcoming Ubuntu release:

https://wiki.ubuntu.com/AppArmor

But yes, I tip my hat to SUSE for being the first to do this.

Reply Parent Bookmark Score: 2

RE[2]: What about appamor?
by SlackerJack on Thu 27th Sep 2007 00:21 in reply to "RE: What about appamor?"
SlackerJack Member since:
2005-11-12

Novell brought AppArmor off another company so it takes the shine off it somewhat, it's not like it's there innovation.

Maybe Novell couldn't be arsed to setup selinux and try something of their own, reminds me of another company.

Reply Parent Bookmark Score: 1