https://bugzilla.novell.com/show_bug.cgi?id=828833 https://bugzilla.novell.com/show_bug.cgi?id=828833#c1 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |UPSTREAM --- Comment #1 from Christian Boltz <suse-beta@cboltz.de> 2013-07-10 14:54:49 CEST --- The problem with the old reporting code is: Yes, it DID work, but it DOES NOT work with current AppArmor versions. One of the reasons are major changes in the audit.log file format. Besides that, the old (upstream) reporting code is extremely hard to maintain (and needs a rewrite or replacement). Nevertheless, I have to partially disagree with you. There IS support for notifications and reports, however it isn't available inside the YaST module anymore. You can use aa-notify to get desktop notifications or can setup an aa-notify | mail cronjob to get a daily or hourly summary (see "man aa-notify" for details). You can also use aa-genprof and aa-logprof (or their YaST interface) to create and update profiles. And finally, you can even read the raw /var/log/audit/audit.log ;-) If you have specific requirements that aa-notify does not cover, feel free to ask upstream (see http://wiki.apparmor.net/index.php/Main_Page#Joining_AppArmor for IRC and mailinglist information). You can also raise the topic of getting notification support in the YaST module back, but I can't promise anything ;-)
From my POV as openSUSE package maintainer: yes, of course I'd like to have notification support in the YaST module again, but I won't be able to implement it and doubt someone else from (open)SUSE will do it. That's why I'm asking you to ask upstream. This also means I have to close this bug as WONTBEABLETOFIX ;-)
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.