From: Szymon Janc <szymon.janc@codecoup.pl>
To: Don Zickus <dzickus@redhat.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Debugging bluetoothd, dbus and selinux help?
Date: Fri, 17 Jun 2016 10:32:23 +0200 [thread overview]
Message-ID: <14376099.m2jF0XBNfH@ix> (raw)
In-Reply-To: <20160615170025.GB90326@redhat.com>
Hi,
On Wednesday 15 June 2016 13:00:25 Don Zickus wrote:
> Hi,
>
> I am trying to debug why bluetoothd decides to disconnect from the d-bus on
> the host, when the client does an object push to an obex agent on the host.
>
> When I set selinux to permissive mode ('setenforce 0'), things work fine (ie
> the object push goes through).
>
> I tried searching /var/log/audit/audit.log, journalctl and dbus-monitor for
> clues (on the host) and can't find anything obvious.
>
> Does anyone have any tips on how to find what security policy might be
> interfering with my test?
>
To me it looks like FD passing on D-Bus is being blocked by SELinux.
--
pozdrawiam
Szymon Janc
next prev parent reply other threads:[~2016-06-17 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 17:00 Debugging bluetoothd, dbus and selinux help? Don Zickus
2016-06-17 8:32 ` Szymon Janc [this message]
2016-06-17 14:43 ` Don Zickus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14376099.m2jF0XBNfH@ix \
--to=szymon.janc@codecoup.pl \
--cc=dzickus@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).