From: Russell Coker <russell@coker.com.au>
To: Lukas Vrabec <lvrabec@redhat.com>, selinux-refpolicy@vger.kernel.org
Subject: Re: New boolean for using bluetooth
Date: Fri, 26 Apr 2019 10:04:11 +1000 [thread overview]
Message-ID: <9B155157-AD74-4349-82E0-C40A1E6DFEF1@coker.com.au> (raw)
In-Reply-To: <87799eb7-b987-3e0a-f3e7-dcd6ddc2bc2d@redhat.com>
SE Linux is based on a default deny model. So failing to allow something means denying it at the lowest levels of policy. So probably a deny boolean is a bad idea.
As for writing a patch, is Fedora still way different from upstream? If so you need to separately do the patch for upstream.
On 26 April 2019 2:58:27 am AEST, Lukas Vrabec <lvrabec@redhat.com> wrote:
>Hi All,
>
>I added new SELinux boolean[1][2] to Fedora SELinux policy called
>deny_bluetooth.
>
>I would like to push it also to refpolicy, however, refpolicy is not
>using bluetooth_socket at all, it's defined in policy but not used by
>any SELinux domain. Can I create patch also with adding these rules
>from
>Fedora policy? And also, for some reason my colleagues didn't follow
>name conventions of global booleans with refpolicy (I didn't find any
>deny_* boolean in refpolicy). So if it make sense to add these kind of
>boolean also to refpolicy, should I defined it as allow_bluetooth ?
>
>[1]https://github.com/fedora-selinux/selinux-policy/commit/54c05f2645a660c545ec406558b42687df2552a7
>[2]
>https://github.com/fedora-selinux/selinux-policy-contrib/commit/5a0561d7b67ae8403d4e1a44acfc8db40ee269a5
>
>Thanks,
>Lukas.
--
Sent from my Huawei Mate 9 with K-9 Mail.
next prev parent reply other threads:[~2019-04-26 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 16:58 New boolean for using bluetooth Lukas Vrabec
2019-04-26 0:04 ` Russell Coker [this message]
2019-04-26 9:02 ` Jason Zaman
2019-04-26 9:23 ` Lukas Vrabec
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=9B155157-AD74-4349-82E0-C40A1E6DFEF1@coker.com.au \
--to=russell@coker.com.au \
--cc=lvrabec@redhat.com \
--cc=selinux-refpolicy@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).