From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Rafael Avila de Espindola <rafael@espindo.la>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Mention disabling SELinux in HACKING
Date: Tue, 19 May 2020 10:57:58 -0700 [thread overview]
Message-ID: <CABBYNZLaA5c=K72qK-W=erURzJiuw-4wkBaBuCuv16HUXsm6Zw@mail.gmail.com> (raw)
In-Reply-To: <87pnazudbo.fsf@espindo.la>
Hi Rafael,
On Tue, May 19, 2020 at 8:58 AM Rafael Avila de Espindola
<rafael@espindo.la> wrote:
>
> So, is this OK?
>
> Cheers,
> Rafael
>
> Rafael Ávila de Espíndola <rafael@espindo.la> writes:
>
> > Running bluetoothd from the build directory I noticed that as soon as
> > a bluetooth audio device was connect, bluetoothd would be disconnected
> > from dbus and print
> >
> > Disconnected from D-Bus. Exiting.
> >
> > Luiz Augusto von Dentz suggested trying with SELinux disabled and that
> > solved the problem.
> >
> > This patch just documents how to disable SELinux before running
> > bluetoothd from the build directory. I would love to say more about
> > why that is needed, but could not find anything on the audit log.
> > ---
> > HACKING | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/HACKING b/HACKING
> > index e10986fcb..29b136b34 100644
> > --- a/HACKING
> > +++ b/HACKING
> > @@ -76,6 +76,9 @@ automatically includes this option.
> > Copy configuration file which specifies the required security policies
> > # sudo cp ./src/bluetooth.conf /etc/dbus-1/system.d/
> >
> > + Disable SELinux
> > + # sudo setenforce 0
> > +
> > Run daemon in foreground with debugging
> > # sudo ./src/bluetoothd -n -d -f ./src/main.conf
> >
> > --
> > 2.26.2
Applied, thanks.
--
Luiz Augusto von Dentz
prev parent reply other threads:[~2020-05-19 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 2:36 [PATCH] Mention disabling SELinux in HACKING Rafael Ávila de Espíndola
2020-05-19 15:58 ` Rafael Avila de Espindola
2020-05-19 17:57 ` Luiz Augusto von Dentz [this message]
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='CABBYNZLaA5c=K72qK-W=erURzJiuw-4wkBaBuCuv16HUXsm6Zw@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=rafael@espindo.la \
/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).