[apparmor] Custom DBUS daemon and apparmor

[Sébastien Sénéchal]

Thanks a lot Tyler,

Here's the bug report : https://bugs.launchpad.net/apparmor/+bug/1252821
If I can help with anything just let me know.

Right now the reason was very obscure as no log activity during rejection

best regards


On 2013-11-19, at 12:02 PM, Tyler Hicks <tyhicks at canonical.com> wrote:

On 2013-11-19 11:03:24, Sébastien Sénéchal wrote:
Hello all

I am writing an app usig remote DBUS for communication

since dbus 1.6.12, apparmor is used for authentication, so i am trying to
find correct way to setup…

this involves:
- a dbus listening on tcp:host=127.0.0.1,bind=*,port=14500

Oof... AppArmor should be disabled if a tcp address is used. The
AppArmor mediation code only has the ability to check peer labels over
UNIX domain sockets. It is most likely seeing an error when getting the
label and then refusing the connection.

It looks like the SELinux mediation support in D-Bus has the same bug:

 https://bugzilla.redhat.com/show_bug.cgi?id=890658

Would you mind opening a bug in Launchpad? I'll fix this for 14.04.

Tyler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/apparmor/attachments/20131119/17c81224/attachment.html>