Hello,
this patch fixes the minitools (aa-audit, aa-complain, aa-enforce,
aa-autodep) to work with multiple profiles at once.
The trick to fix the minitools is to call read_profiles() outside of
the for loop.
References: https://bugs.launchpad.net/apparmor/+bug/1378095
Note: aa-autodep will
On 02/20/2015 08:29 AM, Devon B. wrote:
I'm trying to run AppArmor (2.9.1) against a custom upstream kernel
(3.18.7) but I'm unable to get mount restrictions working.
According to:
http://wiki.apparmor.net/index.php/AppArmor_Core_Policy_Reference#Mount_rules_.28AppArmor_2.8_and_later.29,
Hello,
Am Freitag, 20. Februar 2015 schrieb Seth Arnold:
On Fri, Feb 20, 2015 at 08:23:02PM +0100, Christian Boltz wrote:
this patch makes sure most tools (for example aa-complain) don't
error out if no logfile can be found. (For obvious reasons,
aa-logprof and aa-genprof will still
I'm trying to run AppArmor (2.9.1) against a custom upstream kernel
(3.18.7) but I'm unable to get mount restrictions working.
According to:
http://wiki.apparmor.net/index.php/AppArmor_Core_Policy_Reference#Mount_rules_.28AppArmor_2.8_and_later.29,
mount rules should work since 2.8 but I don't
Hello,
this patch makes sure most tools (for example aa-complain) don't error
out if no logfile can be found. (For obvious reasons, aa-logprof and
aa-genprof will still require a logfile ;-)
This is done by moving code from the global area in aa.py to the new
function set_logfile(), which is
On Fri, Feb 20, 2015 at 08:23:02PM +0100, Christian Boltz wrote:
Hello,
this patch makes sure most tools (for example aa-complain) don't error
out if no logfile can be found. (For obvious reasons, aa-logprof and
aa-genprof will still require a logfile ;-)
This is done by moving code
