** Also affects: apparmor (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu Karmic)
Status: New => Confirmed
** Changed in: apparmor (Ubuntu Karmic)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: apparmor (Ubuntu Karmic)
** Attachment added: "preliminary patch to fix this issue"
http://launchpadlibrarian.net/33755384/bug-446524.patch
--
aa-logprof: doesn't parse new null profile syntax
https://bugs.launchpad.net/bugs/446524
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Marking as In Progress based on Marc's patch.
** Changed in: apparmor (Ubuntu Karmic)
Status: Confirmed => In Progress
--
aa-logprof: doesn't parse new null profile syntax
https://bugs.launchpad.net/bugs/446524
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Changed in: apparmor (Ubuntu Karmic)
Importance: Low => High
** Tags added: regression-potential
--
aa-logprof: doesn't parse new null profile syntax
https://bugs.launchpad.net/bugs/446524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
A feature is still missing from the preliminary patch. When aa-genprof
reloads the profile after prompting the user for changes, the kernel
does not replace the profile on active "null" processes. In order for
active processes to get their profile replaced, the profile name must be
the "null" name.
** Attachment added: "better patch"
http://launchpadlibrarian.net/33796524/bug-446524-v2.patch
--
aa-logprof: doesn't parse new null profile syntax
https://bugs.launchpad.net/bugs/446524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package apparmor - 2.3.1+1403-0ubuntu27
---
apparmor (2.3.1+1403-0ubuntu27) karmic; urgency=low
* utils/SubDomain.pm: handle new format "null" log entries (LP:
#446524)
-- Marc DeslauriersFri, 16 Oct 2009
14:40:04 -0400
** Changed in: apparmor (Ubunt
