[Bug 854351] New: Put back the Notifications Options back in the AppArmor Menu in 12.3 and the missing components in 13.1
https://bugzilla.novell.com/show_bug.cgi?id=854351 https://bugzilla.novell.com/show_bug.cgi?id=854351#c0 Summary: Put back the Notifications Options back in the AppArmor Menu in 12.3 and the missing components in 13.1 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: AppArmor AssignedTo: suse-beta@cboltz.de ReportedBy: secure@aphofis.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Its very easy to manage AppArmor and yet every version you present a different GUI. Could you please put back the Notifications Menu Option for each existing and newly created profiles. In that way, once you have configured a mail sever in Yast any notification coming for Apparmor you can have sent as pop3 IMAP LDAP syslog....so Could you please return the notifications part of Apparmor you have removed in 12.3 and moreso in 13.1 Reproducible: Always Steps to Reproduce: 1.Open Apparmor and you will notice the 'notifications' GUI has been removed and further sanitised. 2. 3. Actual Results: No access to Notifications Expected Results: Software options should never, in principle, be able to be withdrawn; enhanced yes but once your software is out there its a professional ethic's and development convention have clear expectations one of which is, you never remove functionality you fix it Software options should never, in principle, be able to be withdrawn; enhanced yes but once your software is out there its a professional ethic's and development convention have clear expectations one of which is, you never remove functionality you fix it -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=854351 https://bugzilla.novell.com/show_bug.cgi?id=854351#c1 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Christian Boltz <suse-beta@cboltz.de> 2013-12-07 23:48:40 CET --- Welcome back, Scott ;-) I know the status of the YaST AppArmor module is bad, but unfortunately there's not much I can do about it. The code is quite old and needs other old (and not really maintained) perl modules from AppArmor (which is switching to python for the tools like aa-logprof). The code that was used for notifications is unmaintained since years and incompatible with nowaday's log format. Even if I'd re-enable it, the only thing it would do is sending you an always-empty report. This sums up to: This is nothing that needs "some fixes" - the YaST module needs a full rewrite, and the time to do it. IIRC I already told you in your previous bugreport how to setup a cronjob as workaround. Maybe there's also some hope. I have a possible volunteer to rewrite the YaST module, but he seems to be quite busy, which means I can't give you any target date. If you want to get your hands dirty, I'm sure he'll welcome some help ;-) BTW: While I like your "expected result", it is sometimes hard to do it for various reasons. And I'm talking about lots of software, not only YaST. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=854351 https://bugzilla.novell.com/show_bug.cgi?id=854351#c2 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |secure@aphofis.com --- Comment #2 from Scott Couston <secure@aphofis.com> 2013-12-08 18:08:58 EST --- Thanks I understand. We are taught from day 1 at Uni that the answer to a bug in software is never simply remove it...They fill out heads with the principals and concepts concept that you already know; although we haven’t got a multi story Office Tower of maintenance coders working full time 365 days. Happy Christmas..It hot as hell down here in OZ Scott -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=854351 https://bugzilla.novell.com/show_bug.cgi?id=854351#c3 --- Comment #3 from Christian Boltz <suse-beta@cboltz.de> 2013-12-08 14:46:56 CET --- (In reply to comment #2)
We are taught from day 1 at Uni that the answer to a bug in software is never simply remove it...
Yes, that's the theory. Unfortunately practise often differs - and always wins...
They fill out heads with the principals and concepts concept that you already know; although we haven’t got a multi story Office Tower of maintenance coders working full time 365 days.
;-)
Happy Christmas..It hot as hell down here in OZ
Happy Christmas! (and BTW, the weather in germany is not really hot - but if we are lucky, we get some snow for christmas ;-) -- 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.
participants (1)
-
bugzilla_noreply＠novell.com