** Changed in: apparmor
Status: Fix Committed => Fix Released
** Changed in: apparmor/2.10
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
"Real fix" (which decides about file vs. network instead of ignoring
these events) implemented in bzr trunk r3594 and 2.10 branch r3369.
** Changed in: apparmor
Assignee: (unassigned) => Christian Boltz (cboltz)
** Also affects: apparmor/2.10
Importance: Undecided
Status: New
**
This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.2
---
apparmor (2.10.95-0ubuntu2.2) xenial; urgency=medium
* r3498-r3499-ignore-net-events-that-look-like-file-events.patch: Prevent an
aa-logprof crash by ignoring file events that contains send *and* receive
in
This bugreport is getting quite long ;-) and starts to get confusing.
I just opened https://bugs.launchpad.net/apparmor/+bug/1613061 as
reminder that logparser.py needs to switch based on the event details
instead of the operation= keyword.
The crashes reported in this bug are (hot)fixed in all
I've thoroughly tested apparmor 2.10.95-0ubuntu2.2 in xenial-proposed.
I've verified that this bug is fixed (via the Test Case in the
description) and I've also went through the AppArmor Test Plan
(excluding the Ubuntu Touch specific tests):
Hello Neil, or anyone else affected,
Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Impact]
+
+ AppArmor policy developers cannot use aa-logprof without it exiting with
+ a traceback on certain denial messages.
+
+ [Test Case]
+
+ $ echo 'type=AVC msg=audit(1463403689.381:267599): apparmor="ALLOWED" \
+ operation="file_perm" profile="foo" pid=13215
This bug was fixed in the package apparmor - 2.10.95-4ubuntu2
---
apparmor (2.10.95-4ubuntu2) yakkety; urgency=medium
* Drop the following change now that click-apparmor has been updated:
- Continue installing aa-exec into /usr/sbin/ for now since
click-apparmor's
** Branch linked: lp:~apparmor-dev/apparmor/apparmor-ubuntu-citrain
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1582374
Title:
Log contains unknown mode senw
Status
How do I apply the above mentioned hotfix?
Writing updated profile for /usr/bin/konversation.
Setting /usr/bin/konversation to complain mode.
Before you begin, you may wish to check if a
profile already exists for the application you
wish to confine. See the following wiki page for
more
I have the issue as well, newly installed kubuntu 16.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1582374
Title:
Log contains unknown mode senw
Status in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Hotfix commited to bzr trunk r3460, 2.10 branch r and 2.9 branch
r3011.
This hotfix avoids the crash by ignoring these events. The long-term fix
will be to handle these events as what they are - network events, but
that will need some bigger changes.
--
You received this bug notification
** Branch linked: lp:apparmor
** Branch linked: lp:apparmor/2.10
** Branch linked: lp:apparmor/2.9
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1582374
Title:
Log
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
16 matches
Mail list logo
