On Wed, Aug 17, 2011 at 03:42:12PM +0530, phanisvara das wrote:
On Wed, 17 Aug 2011 14:52:13 +0530, Per Jessen <per@opensuse.org> wrote:
jdd wrote:
Le 16/08/2011 18:39, phanisvara das a écrit :
no problem really; i just un-install it as soon as it tries to block something i need (which happens soon after every fresh install of oS).
I install 50 machines each year (approx) an never had apparmor block anything.
I second that, although I don't do that many installs. I've filed a couple of bugreports on minor apparmor issues, but I've never needed to disable it.
i admit that the last time i actually looked into what apparmor was doing has been a long time ago. i guess i'll give it another try, if only to help debugging something that does have it's uses, though i still consider it unnecessary for myself.
It usually is not enabled for most things.
We enabled it for nmbd and smbd in 11.4, which due to very flexible nature of smb paths that can be served made it reject valid user scenarios. It is kind of hard to confine a service which offers read/write access to configurable paths.
Ciao, Marcus Hmm, sounds like a problematic addition. Maybe the restrictions should be
On Wednesday, August 17, 2011 04:34:46 AM Marcus Meissner wrote: lifted then. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org