** Changed in: apparmor
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.
https://bugs.launchpad.net/bugs/1540562
Title:
aa-genprof crashes in logparser
"Real fix" (which decides about file vs. network instead of ignoring
these events) implemented in bzr trunk r3594 and 2.10 branch r3369 (will
be in 2.10.2).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Branch linked: lp:apparmor
** Branch linked: lp:apparmor/2.10
--
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/1540562
Title:
aa-genprof crashes in logparser NoneType
** 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.
https://bugs.launchpad.net/bugs/1540562
Title:
aa-genprof crashes in logparser
** Changed in: apparmor/2.9
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.
https://bugs.launchpad.net/bugs/1540562
Title:
aa-genprof crashes in logparser
This bug was fixed in the package apparmor - 2.10.95-0ubuntu1
---
apparmor (2.10.95-0ubuntu1) xenial; urgency=medium
* Update to apparmor 2.10.95 (2.11 Beta 1) (LP: #1561762)
- Allow Apache prefork profile to chown(2) files (LP: #1210514)
- Allow deluge-gtk and
I note the original bug report was for Ubuntu 16.04. I've just
experienced the exact same error (minor line number changes
notwithstanding) as the original reporter.
I'm using 14.04.4 LTS and have 2.8.95~2430-0ubuntu5.3 installed. Will
this fix come down the 2.8 branch for 14.04 LTS users, too,
Fix commited to bzr trunk r3368, 2.10 branch r3308 and 2.9 branch r2993.
** Changed in: apparmor
Assignee: (unassigned) => Christian Boltz (cboltz)
** Changed in: apparmor
Milestone: None => 2.10.1
** Changed in: apparmor
Status: New => Fix Committed
** Changed in:
Relevant log line (profile name changed to make reproducing easier):
Feb 1 14:34:25 zippy kernel: [55870.767873] audit: type=1400
audit(1454355265.041:133046): apparmor="ALLOWED"
operation="file_receive" profile="/usr/sbin/smbd" pid=28265
comm="RosettaStoneDae" family="inet" sock_type="stream"
e dict that causes problem: {'task': 0, 'info': None, 'attr': None,
'denied_mask': None, 'time': 1454361312, 'parent': 0, 'name': None,
'active_hat': None, 'resource': None, 'request_mask': None, 'pid':
31472, 'operation': 'file_receive', 'name2': None, 'error_code': 0,
'magic_token': 0,
Yes, that's also what I found.
Patch sent to the mailinglist for review.
If you want to test it, get logparser.py from the bzr 2.10 branch (there
were several fixes since 2.10) and around line 304, change
if e['operation'] in ['file_perm', 'file_inherit'] and not
e['request_mask']:
11 matches
Mail list logo
