[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200710262244.57147.agruen@suse.de>
Date: Fri, 26 Oct 2007 22:44:56 +0200
From: Andreas Gruenbacher <agruen@...e.de>
To: Arjan van de Ven <arjan@...radead.org>
Cc: jjohansen@...e.de, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [AppArmor 00/45] AppArmor security module overview
On Friday 26 October 2007 16:37, Arjan van de Ven wrote:
> In addition, I'd like to ask you to put a file in Documentation/
> somewhere that describes what AppArmor is intended security protection
> is (it's different from SELinux for sure for example); by having such a
> document for each LSM user, end users and distros can make a more
> informed decision which module suits their requirements... and it also
> makes it possible to look at the implementation to see if it has gaps
> to the intent, without getting into a pissing contest about which
> security model is better; but unless the security goals are explicitly
> described that's a trap that will keep coming back... so please spend
> some time on getting a good description going here..
Hmm, I agree that it makes sense to give a short overview of each LSM. A
description of the AppArmor model and implementation can be found in the
directory that John referred to actually. I'm unsure how much of that makes
sense under Documentation/ -- what do you think?
http://forgeftp.novell.com/apparmor/LKML_Submission-Oct-07/techdoc.pdf
I guess actual end user information doesn't belong in the kernel sources; that
really seems wrong.
Thanks,
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists