https://bugzilla.novell.com/show_bug.cgi?id=717152
https://bugzilla.novell.com/show_bug.cgi?id=717152#c4
Scott Couston changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |REOPENED
Resolution|WONTFIX |
QAContact|qa@suse.de |jsuchome@suse.com
--- Comment #4 from Scott Couston 2011-09-16 21:59:21 UTC ---
I cant get more precise about the bug profile of functionality with Apparmour
that does not function. If you want to close this as wontfix - You must close
all dependency with the same reason.
Jiri can you sort this out please and as a degree of logic here !
How much more precise do your need from me?
To quote the dependant bug
--- Comment #5 from Scott Couston 2011-09-08 07:25:21 UTC
---
In all seriousness I think the whole Yast Module front end to Apparmour needs a
TOTAL rewrite after much reflection.
The module has no real thought progression form in its current useless state
1 Turning it on with options to add new learned profiles
2 Notification types and severity's on each profile
3 Changing it with options to email notifications (POP) VIA TLS/SSL + sendmail
4 Demand Reporting options to screen or printer
Comprehensive help screen within yast help + add every apparmour event to audit
logs for applications the centrally view, read and act on hundreds of PC's -
Complex Event Processing Application - already exist The only trouble with
apparmour as it is now, the user has no idea if its working or doing anything.
Its not a big ask to expect final QA certification of the state of the original
and current module +Actually working and the GUI interface actually doing
something -Sorry guys we dont need to be wise in hindsight to expect this basic
level of quality
--
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.