I have just encountered this issue (while trying to figure out why aa-
genprof could not correctly profile a script). This is a pretty crazy
issue to be remaining open for so long... one of the two major LSM
systems not logging correctly and therefore having logs not appear in
ausearch (not to ment
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117804
Title:
ausearch doesn't show AppArmor denial messages
To manage notifications about this bug go to:
https://bugs.launchpad.
Meta: I've re-read the discussion from December 2017. If there were
messages later than this on the thread, I missed them due to suboptimal
mailing list archive presentation. Sorry if this leads me to wrong
conclusions!
I lack the skills to do the actual work I think should be done. The only
way I
There was an attempt to revive this Dec. 6, 2017
https://lists.ubuntu.com/archives/apparmor/2017-December/011370.html
upstream there is belief in using a generic audit message types. The
problem is that apparmor, selinux and smack messages differ, so they
aren't so common.
This is going to have
IMHO we have to ask John Johansen about this, he's working on kernel
side.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117804
Title:
ausearch doesn't show AppArmor denial messages
To manage noti
FTR this was raised as a potential blocker for enabling AppArmor by
default on Debian: https://bugs.debian.org/872726. I'm going to
investigate why this is a blocker there.
tl;dr: as the audit maintainers said in 2014
(https://www.redhat.com/archives/linux-audit/2014-May/msg00119.html) and
2016 (h
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117804
Title:
ausearch doesn't show AppArmor denial messages
To manage not
I have asked about it in audit mailing list [0], and Audit developer
said that AppArmor should use assigned event numbers in right way, or
something like that..
[0] https://www.redhat.com/archives/linux-audit/2016-April/msg00129.html
--
You received this bug notification because you are a member
** Changed in: audit (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => (unassigned)
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Importance: Undecided => Low
** Changed in: apparmor
Status: New => Confirmed
--
You received this bug noti
** Tags added: apparmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117804
Title:
ausearch doesn't show AppArmor denial messages
To manage notifications about this bug go to:
https://bugs.launch
This bug is, I think, currently discussed on the linux-audit
mailinglist:
https://www.redhat.com/archives/linux-audit/2014-May/msg00094.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117804
Titl
** Changed in: audit (Ubuntu)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117804
Title:
ausearch doesn't show AppArmor denial messages
To man
12 matches
Mail list logo
