linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Jakub Tyszkowski <jakub.tyszkowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] android/init: Update init script with proper selinux domain label
Date: Tue, 25 Nov 2014 14:16:31 +0100	[thread overview]
Message-ID: <2625784.YzjpYWiJ5O@leonov> (raw)
In-Reply-To: <1416578301-11341-1-git-send-email-jakub.tyszkowski@tieto.com>

Hi Jakub,

On Friday 21 of November 2014 14:58:21 Jakub Tyszkowski wrote:
> This is to get rid of SEPolicy complain about service running without
> defined policies.
> ---
>  android/init.bluetooth.rc | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/android/init.bluetooth.rc b/android/init.bluetooth.rc
> index af62121..1815fac 100644
> --- a/android/init.bluetooth.rc
> +++ b/android/init.bluetooth.rc
> @@ -25,6 +25,7 @@ service bluetoothd /system/bin/logwrapper
> /system/bin/bluetoothd class main
>      # init does not yet support setting capabilities so run as root,
>      # bluetoothd drop uid to bluetooth with the right linux capabilities
> +    seclabel u:r:bluetoothd:s0
>      group bluetooth
>      disabled
>      oneshot
> @@ -33,6 +34,7 @@ service bluetoothd-snoop /system/bin/logwrapper
> /system/bin/bluetoothd-snoop class main
>      # init does not yet support setting capabilities so run as root,
>      # bluetoothd-snoop drops unneeded linux capabilities
> +    seclabel u:r:bluetoothd:s0
>      group nobody
>      disabled
>      oneshot

I think we should have separate policy for snoop service as it requires far 
less permissions to run.

-- 
BR
Szymon Janc

      reply	other threads:[~2014-11-25 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 13:58 [PATCH] android/init: Update init script with proper selinux domain label Jakub Tyszkowski
2014-11-25 13:16 ` Szymon Janc [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=2625784.YzjpYWiJ5O@leonov \
    --to=szymon.janc@tieto.com \
    --cc=jakub.tyszkowski@tieto.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).