From: cwarner <cwarner@kernelcode.com>
To: Erich Schubert <erich@debian.org>
Cc: Daniel J Walsh <dwalsh@redhat.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: FYI SELinux/AppArmor press
Date: Tue, 28 Feb 2006 22:20:25 -0500 [thread overview]
Message-ID: <1141183226.8475.22.camel@localhost.localdomain> (raw)
In-Reply-To: <1141138934.29803.2.camel@wintermute.xmldesign.de>
On Tue, 2006-02-28 at 16:02 +0100, Erich Schubert wrote:
> Hello Daniel, Hello SELinux list,
> I've posted a rather critical reply to the "AppArmor vs. SELinux"
> discussion to my blog at http://blog.drinsama.de/erich/en/linux/selinux
>
> In my opinion, AppArmor can indeed kill SELinux, even when it provides
> much lesser security - by just incorporating the community better than
> SELinux does.
>
> best regards,
> Erich Schubert
I think everyone is mostly aware of the documentation issue, that said.
Seeing as everyone keeps saying easier to use. Can you state an explicit
example please? From Crispin Corwan's slides and the constant "easier to
use" barrage I'd expect an example.
How is AppArmor easier to use? Negating the fact that I would have to
learn something new.
--
Christopher Warner
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-03-01 3:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 21:01 FYI SELinux/AppArmor press Daniel J Walsh
2006-02-25 5:39 ` Randal T. Rioux
2006-02-28 15:02 ` Erich Schubert
2006-03-01 3:20 ` cwarner [this message]
2006-03-01 14:12 ` Erich Schubert
2006-03-01 20:59 ` Benjy Grogan
2006-03-01 22:00 ` Erich Schubert
2006-03-02 2:47 ` Chad Sellers
2006-03-02 10:43 ` Erich Schubert
2006-03-03 1:19 ` Joshua Brindle
2006-03-03 13:21 ` Erich Schubert
2006-03-03 16:50 ` coderman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1141183226.8475.22.camel@localhost.localdomain \
--to=cwarner@kernelcode.com \
--cc=dwalsh@redhat.com \
--cc=erich@debian.org \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.