https://bugzilla.novell.com/show_bug.cgi?id=717152 https://bugzilla.novell.com/show_bug.cgi?id=717152#c Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |531512 -- 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=717152 https://bugzilla.novell.com/show_bug.cgi?id=717152#c2 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |scott@aphofis.com Resolution|INVALID | --- Comment #2 from Scott Couston 2011-09-16 01:09:21 UTC --- I would suggest you read the dependency...The bugs are so serious with Apparmour and the Suse Firewall and with Apparmour they need fixing NOW. The problem with Apparmour is that to correct this a total rewrite of the Yast front end is indicated. - In the grant scheme of both Apparmour I have supplied detailed faults, offered a quick fix and offered the best fix for both here in this bug report. Given the desire to fix both for good I have set a target on 12.1 otherwise close ALL of them as WONTFIX -- 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=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.

https://bugzilla.novell.com/show_bug.cgi?id=717152 https://bugzilla.novell.com/show_bug.cgi?id=717152#c6 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|security-team@suse.de |jsrain@suse.com QAContact|jsuchome@suse.com |qa@suse.de OS/Version|SuSE Other |openSUSE 11.3 --- Comment #6 from Scott Couston 2011-10-04 22:14:18 UTC --- My Apologies - The faults described here were taken fro RC 11.3 - its the same as in 11.1 but for clarity I have corrected the version the bugs came from. Given that we dont know if Apparmour does anything at all, and only has questionable notifications if system mail is both set and configured, and the Global movement to far greater security; 12.1 was selected for hopeful fix. The dependency bug indicates the failings of the current firewall in respect to functionality and usability and again notification of events is poorly dealt with. If we are to commit man hours to correct Apparmour then I think it would be equally as both are complementary and both can use the same code written as far as the notification mechanism at the very least. important to re-evaluate Suse Firewall. In both these bugs I am qualified to discuss highly technical aspects of functionality, admittedly I cant write the Yast front end code - I am happy to discuss and talk in highly technical security terms for both Apparmour and the SPI of Suse Firewall -- 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=717152 https://bugzilla.novell.com/show_bug.cgi?id=717152#c8 --- Comment #8 from Scott Couston 2011-10-05 21:16:35 UTC --- No Problem Jiri...Had a lot of trouble with bug status - see history - I just wanted you to sort it out and reassign to the correct person...thanks...Yes Its complementary to 'security in total' which includes apparmour - This bug is all about Suse Firewall but much of the improvements to the way notification can be done would be common to Apparmour. No sense fixing Apparmour when we still allow anyone to come in our front door with only token resistance -- 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=717152 https://bugzilla.novell.com/show_bug.cgi?id=717152#c9 --- Comment #9 from Scott Couston 2011-11-30 21:58:04 UTC --- At the very least can we just add syslog traffic from the firewalls logs to outbound traffic on UDP514, and use the default categories for syslog severity and include the log text in the rest of the traffic. At least that way people who run a syslog server can see the log messages dynamically as they occur. Its usual human thought that if you cant see what the logs of DROP or CLOSE or anything else, they think it does not do anything. Can we also add functionality to send out POP/IMAP email to be configurable to the default defined syslog priorities and be able to end out an email if 'error level' is selected by the user. We would need all email fields - my suggestion that yast has one and one only place to configure to send out all POP/IMAP emails for all Yast applications were not deemed useful -- 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=717152 https://bugzilla.novell.com/show_bug.cgi?id=717152#c Bug 717152 depends on bug 531512, which changed state. Bug 531512 Summary: Yast AppArmor - Serious Problems with the WHOLE Collection -Strongly Suggest Total Rewrite http://bugzilla.novell.com/show_bug.cgi?id=531512 What |Old Value |New Value ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Status|NEEDINFO |RESOLVED Resolution| |WONTFIX -- 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=717152 https://bugzilla.novell.com/show_bug.cgi?id=717152#c Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|531512 | -- 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.