From: "Von Dentz, Luiz" <luiz.von.dentz@intel.com>
To: Inga Stotland <inga.stotland@intel.com>
Cc: linux-bluetooth@vger.kernel.org, "Gix, Brian" <brian.gix@intel.com>
Subject: Re: [PATCH BlueZ] mesh: Add D-Bus policy for Bluetooth mesh daemon
Date: Fri, 18 Jan 2019 05:04:23 -0300 [thread overview]
Message-ID: <CACumGOLC+b1WsfSqgXLRBQbeZ0vFOx6bpLAFjrpYBXvrQ5oxig@mail.gmail.com> (raw)
In-Reply-To: <20190118034652.4018-1-inga.stotland@intel.com>
Hi Inga,
On Fri, Jan 18, 2019 at 12:47 AM Inga Stotland <inga.stotland@intel.com> wrote:
>
> This adds new D-Bus policy file btmesh.conf
> ---
> Makefile.mesh | 6 ++++++
> mesh/btmesh.conf | 24 ++++++++++++++++++++++++
> 2 files changed, 30 insertions(+)
> create mode 100644 mesh/btmesh.conf
>
> diff --git a/Makefile.mesh b/Makefile.mesh
> index ea6c5e939..e15718116 100644
> --- a/Makefile.mesh
> +++ b/Makefile.mesh
> @@ -1,5 +1,9 @@
> if MESH
>
> +if DATAFILES
> +dbus_DATA += mesh/btmesh.conf
> +endif
> +
> mesh_sources = mesh/mesh.h mesh/mesh.c \
> mesh/net_keys.h mesh/net_keys.c \
> mesh/mesh-io.h mesh/mesh-io.c \
> @@ -27,4 +31,6 @@ libexec_PROGRAMS += mesh/meshd
> mesh_meshd_SOURCES = $(mesh_sources) mesh/main.c
> mesh_meshd_LDADD = src/libshared-ell.la $(ell_ldadd) -ljson-c
> mesh_meshd_DEPENDENCIES = $(ell_dependencies) src/libshared-ell.la
> +
> +EXTRA_DIST += mesh/btmesh.conf
> endif
> diff --git a/mesh/btmesh.conf b/mesh/btmesh.conf
> new file mode 100644
> index 000000000..f05545065
> --- /dev/null
> +++ b/mesh/btmesh.conf
> @@ -0,0 +1,24 @@
> +<!-- This configuration file specifies the required security policies
> + for Bluetooth Mesh daemon to work. -->
> +
> +<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
> + "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
> +<busconfig>
> +
> + <!-- ../system.conf have denied everything, so we just punch some holes -->
> +
> + <policy user="root">
> + <allow own="org.bluez.mesh"/>
> + <allow send_destination="org.bluez.mesh"/>
> + <allow send_interface="org.bluez.mesh.Application1"/>
> + <allow send_interface="org.bluez.mesh.Element1"/>
> + <allow send_interface="org.bluez.mesh.ProvisionAgent1"/>
> + <allow send_interface="org.freedesktop.DBus.ObjectManager"/>
> + <allow send_interface="org.freedesktop.DBus.Properties"/>
> + </policy>
> +
> + <policy context="default">
> + <allow send_destination="org.bluez.mesh"/>
> + </policy>
> +
> +</busconfig>
> --
> 2.17.2
Any plans to put together a btmesh.service file for systemd as well?
next prev parent reply other threads:[~2019-01-18 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 3:46 [PATCH BlueZ] mesh: Add D-Bus policy for Bluetooth mesh daemon Inga Stotland
2019-01-18 8:04 ` Von Dentz, Luiz [this message]
2019-01-19 3:54 ` Stotland, Inga
2019-01-18 8:50 ` Marcel Holtmann
2019-01-19 3:49 ` Stotland, Inga
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=CACumGOLC+b1WsfSqgXLRBQbeZ0vFOx6bpLAFjrpYBXvrQ5oxig@mail.gmail.com \
--to=luiz.von.dentz@intel.com \
--cc=brian.gix@intel.com \
--cc=inga.stotland@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.