[Bug 1700231] Re: 16.04 , apparmor denies dbus communications even with flags=(complain)

2017-06-27 Thread Tyler Hicks
@sles the supported way to move the entire profile and all subprofiles into complain mode is via the aa-complain utility in the apparmor-utils package. You may find that easier than manually adjusting individual profile flags. -- You received this bug notification because you are a member of

[Bug 1700231] Re: 16.04 , apparmor denies dbus communications even with flags=(complain)

2017-06-27 Thread Jamie Strandboge
@sles, yes, this is expected behavior. The child profile 'inside' is still a separate profile and therefore needs to have its own flags. Marking this bug as Invalid based on reporter's feedback. If you feel this is in error, please reopen. Thanks for filing a bug and please feel free to file bugs

[Bug 1700231] Re: 16.04 , apparmor denies dbus communications even with flags=(complain)

2017-06-26 Thread sles
Well, may be this is not bug, but expected behaviour. /etc/apparmor.d/usr.sbin.ejabberdctl contains /usr/sbin/ejabberdctl { profile su { ... } } I.e. there is profile su inside. If I add: /usr/sbin/ejabberdctl flags=(complain) { it doesn't changeprofile su behaviour. I

[Bug 1700231] Re: 16.04 , apparmor denies dbus communications even with flags=(complain)

2017-06-26 Thread Tyler Hicks
Hello - Thanks for the bug report! I'm unable to reproduce the behavior that you're experiencing. Please include more information about your environment such as the apparmor package version and kernel version (/proc/version_signature). Here's how I tested: $ cmd="dbus-send --print-reply