Doing the same test on Hardy i386 virtual machine and on real i386 hardware resulted in: $ sudo aa-genprof $HOME/foobar.sh Writing updated profile for /home/jamie/foobar.sh. Setting /home/jamie/foobar.sh to complain mode.
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: /home/jamie/foobar.sh [(S)can system log for SubDomain events] / (F)inish Reading log entries from /var/log/messages. Updating AppArmor profiles in /etc/apparmor.d. Log contains unknown mode 1236777289.604:351):. Hardy i386 kern.log entries are attached. This is a ** Attachment added: "sec-hardy-i386_kern.log" http://launchpadlibrarian.net/23752788/sec-hardy-i386_kern.log -- aa-genprof creates empty profiles from /var/log/messages entries (works fine with auditd) https://bugs.launchpad.net/bugs/340183 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
