-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/16/2011 09:50 AM, Marcus Meissner wrote:

On Sun, May 15, 2011 at 07:08:21AM -0700, Roger Luedecke wrote:

...

Even SELinux has this. It is bad news for people unfamiliar with AppArmor if it decides to block something. The average casual home user will find the e-mail notification not only complicated, but largely unnecessary. The YaST modules make AppArmor management relatively simple, now we just need to make knowing they need to be used simple. Should I add this in openFATE also?

There was a long standing fate, 302476.

So far 12.1 is not added, but you can add it.

Then it just needs someone to do it :(

The apparmor-dbus package in security:apparmor is probably a good start for that. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3RK+gACgkQLPWxlyuTD7LAoACfYOJeDr6mcKAyNGbsVMEC0rlY QwAAnRvIyRLzzLulHbhbDHtkDFo0tjmF =SVru -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Mon, May 16, 2011 at 06:55:40AM -0700, Roger Luedecke wrote:

Frankly, it seems like a rather large oversight.

Given that the model of apparmor protection was for servers, where such a notifier wouldn't make much sense, or even work, it is not. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/16/2011 09:50 AM, Marcus Meissner wrote:

On Sun, May 15, 2011 at 07:08:21AM -0700, Roger Luedecke wrote:

...

Even SELinux has this. It is bad news for people unfamiliar with AppArmor if it decides to block something. The average casual home user will find the e-mail notification not only complicated, but largely unnecessary. The YaST modules make AppArmor management relatively simple, now we just need to make knowing they need to be used simple. Should I add this in openFATE also?

There was a long standing fate, 302476.

So far 12.1 is not added, but you can add it.

Then it just needs someone to do it :(

The apparmor-dbus package in security:apparmor is probably a good start for that. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3RK+gACgkQLPWxlyuTD7LAoACfYOJeDr6mcKAyNGbsVMEC0rlY QwAAnRvIyRLzzLulHbhbDHtkDFo0tjmF =SVru -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Mon, May 16, 2011 at 06:55:40AM -0700, Roger Luedecke wrote:

Frankly, it seems like a rather large oversight.

Given that the model of apparmor protection was for servers, where such a notifier wouldn't make much sense, or even work, it is not. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org