aa-genprof fails with "Use of uninitialized value in split"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apparmor (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Hello,
I tried to create a apparmor profile for wine today. I proceeded as normal when invoking aa-genprof
"root@mybox:~# aa-genprof wine"
At the beginning things looked as usual and I fired up wine with the game Fallout, but when I then tried to parse the log things became ugly
<START aa-genprof output>
Please start the application to be profiled in
another window and exercise its functionality now.
Once completed, select the "Scan" button below in
order to scan the system logs for AppArmor events.
For each AppArmor event, you will be given the
opportunity to choose whether the access should be
allowed or denied.
Profiling: /usr/bin/wine
[(S)can system log for SubDomain events] / (F)inish
Reading log entries from /var/log/messages.
Updating AppArmor profiles in /etc/apparmor.d.
Use of uninitialized value in split at /usr/share/
Use of uninitialized value in string ne at /usr/share/
Log contains unknown mode mce=rofile.
<END aa-genprof>
I am no perl programmer, but to me this looks like some memory that was over-written which wasn't supposed to...
I tried the procedure also with the autorun.exe of Diablo, the same thing happened. Interestingly though this is what I received from trying the same with ping:
<START aa-genprof output>
Reading log entries from /var/log/messages.
Updating AppArmor profiles in /etc/apparmor.d.
Complain-mode changes:
Profile: /bin/ping
Capability: net_raw
Severity: 8
[(A)llow] / (D)eny / Abo(r)t / (F)inish
<END aa-genprof>
My system is set up as follows:
Ubuntu 8.04 (AMD64), distribution kernel 2.6.24-16-generic
Intel C2D
I hope this makes more sense to you than to me, and thank you for your time.
Best regards
Stian Johnsen
summary: |
- aa-genprof fails at wine + aa-genprof fails with "Use of uninitialized value in split" |
Changed in apparmor (Ubuntu): | |
status: | New → Confirmed |
This should be fixed in the latest apparmor packages. Can you try in either Ubuntu 9.10 or an up-to-date 8.04 LTS (as initially reported by you). Thanks!