|| ||John Johansen <firstname.lastname@example.org> |
|| ||email@example.com |
|| ||[AppArmor #5 0/13] AppArmor security module |
|| ||Wed, 14 Jul 2010 17:43:28 -0700|
|| ||Article, Thread
This is the fifth general posting of the newest version of the
AppArmor security module it has been rewritten to use the security_path
hooks instead of the previous vfs approach. The current implementation
is aimed at being as semantically close to previous versions of AppArmor
as possible while using the existing LSM infrastructure.
Development is on going and
improvements to file, capability, network, resource usage and ipc mediation
With this submission we believe AppArmor is ready for inclusion into
_Issues NOT specifically addressed_
* The d_namespace_path function still manually strips the " (deleted)"
string that __d_path appends. A fix to __d_path is being pursued
independently of the AppArmor submission.
_Issues Addressed Since Last Time AppArmor was Posted_
* AppArmor auditing has been converted to use lsm_audit as suggested by
Eric Paris in
* The user space interface CONFIG_APPARMOR_COMPAT_24 has not been removed,
as the replacement interface isn't ready yet. It will become a separate
patch that distros can carry to provide backwards compatibility.
* AppArmor's old network mediation has been removed and moved into
the compatibility patch. The new network mediation routines will
be submitted for review separate for the AppArmor base.
* all issues raised from last posting should be addressed.
* The code has seen more cleanup removing dead code. eg. // as null transition
* Several bug fixes have been applied
A Detailed list of all changes and patches are available from the AppArmor
The AppArmor project has recently transitioned away from Novell forge.
Code and Documentation can be found at the following locations
* Mailing List - firstname.lastname@example.org
* Documentation (wip) - http://apparmor.wiki.kernel.org/
* User space tools - https://launchpad.net/apparmor
* Kernel module -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/