Message	SHA1
AppArmor: add "file" details to securityfs ... Create the "file" directory in the securityfs for tracking features related to files. Signed-off-by: Kees Cook <kees@ubuntu.com> Signed-off-by: John Johansen <john.johansen@canonical.com> Kees Cook   authored and   John Johansen   commited 2012-02-27 11:38:18 -08:00	a9bf8e9fd5
AppArmor: add initial "features" directory to securityfs ... This adds the "features" subdirectory to the AppArmor securityfs to display boolean features flags and the known capability mask. Signed-off-by: Kees Cook <kees@ubuntu.com> Signed-off-by: John Johansen <john.johansen@canonical.com> Kees Cook   authored and   John Johansen   commited 2012-02-27 11:38:17 -08:00	e74abcf335
AppArmor: refactor securityfs to use structures ... Use a file tree structure to represent the AppArmor securityfs. Signed-off-by: Kees Cook <kees@ubuntu.com> Signed-off-by: John Johansen <john.johansen@canonical.com> Kees Cook   authored and   John Johansen   commited 2012-02-27 11:38:09 -08:00	9acd494be9
AppArmor: userspace interfaces ... The /proc/<pid>/attr/* interface is used for process introspection and commands. While the apparmorfs interface is used for global introspection and loading and removing policy. The interface currently only contains the files necessary for loading policy, and will be extended in the future to include sysfs style single per file introspection inteface. The old AppArmor 2.4 interface files have been removed into a compatibility patch, that distros can use to maintain backwards compatibility. Signed-off-by: John Johansen <john.johansen@canonical.com> Signed-off-by: James Morris <jmorris@namei.org> John Johansen   authored and   James Morris   commited 2010-08-02 15:35:13 +10:00	63e2b42377