From: Stephen Smalley <sds@tycho.nsa.gov>
To: Richard Haines <richard_c_haines@btinternet.com>,
selinux@vger.kernel.org, paul@paul-moore.com
Subject: Re: [PATCH V4 0/3] selinux-testsuite: Add BPF tests
Date: Wed, 18 Sep 2019 11:41:23 -0400 [thread overview]
Message-ID: <a43a310c-346e-60b8-bf45-9c7663e73c89@tycho.nsa.gov> (raw)
In-Reply-To: <20190917145640.25629-1-richard_c_haines@btinternet.com>
On 9/17/19 10:56 AM, Richard Haines wrote:
> Patch 1 Runs basic checks for BPF with map_create, map_read, map_write,
> prog_load and prog_run permissions.
> V2 Change - Split BPF code into bpf_common.c for others to use.
> V3 Changes - Correct style, Fix typos
> V4 Changes - Fixes as discussed in [1]
>
> Patch 2 Updates fdreceive to test BPF security_file_receive() path using
> the common BPF code in tests/bpf.
> V2 Change - Added to use tests/bpf/bpf_common.c for BPF tests.
> V3 Changes - Run tests under tests/bpf not tests/fdreceive, fix typos.
> V4 Changes - Update to work with changes in [1]
>
> Patch 3 - Updates Binder to test BPF path security_binder_transfer_file()
> V4 Change - New patch
With this version of the patches, all of the tests pass for me,
including the binder tests on a kernel with binder enabled.
The audit log output lined up correctly with the expected denials.
There was a fair amount of noise that had to be filtered/ignored though
due to the sys_admin checks (for bpf) and sys_nice checks (for binder),
which apparently aren't fatal to the system calls. We might want to
have a look sometime at avoiding unnecessary CAP_SYS_ADMIN and
CAP_SYS_NICE checks in the bpf and binder code to avoid polluting the
audit logs and leading people to generate overly permissive policies.
That's not your bug to fix though.
>
> [1] https://lore.kernel.org/selinux/19b043bc4d5efbf2f1994958c0a74709a34e3ad0.camel@btinternet.com/
>
> Richard Haines (3):
> selinux-testsuite: Add BPF tests
> selinux-testsuite: Add BPF support to fdreceive test
> selinux-testsuite: Add BPF support to binder test
>
> README.md | 4 +-
> defconfig | 5 +
> policy/Makefile | 4 +
> policy/test_binder_bpf.te | 73 ++++++++++++
> policy/test_bpf.te | 78 +++++++++++++
> policy/test_fdreceive_bpf.te | 60 ++++++++++
> tests/Makefile | 7 ++
> tests/binder/Makefile | 5 +
> tests/binder/binder_common.c | 10 +-
> tests/binder/binder_common.h | 17 ++-
> tests/binder/client.c | 28 ++++-
> tests/binder/manager.c | 2 +-
> tests/binder/service_provider.c | 118 ++++++++++++++-----
> tests/bpf/.gitignore | 2 +
> tests/bpf/Makefile | 17 +++
> tests/bpf/bpf_common.c | 53 +++++++++
> tests/bpf/bpf_common.h | 34 ++++++
> tests/bpf/bpf_test.c | 77 ++++++++++++
> tests/bpf/test | 199 ++++++++++++++++++++++++++++++++
> tests/fdreceive/Makefile | 14 ++-
> tests/fdreceive/client.c | 93 +++++++++++++--
> 21 files changed, 847 insertions(+), 53 deletions(-)
> create mode 100644 policy/test_binder_bpf.te
> create mode 100644 policy/test_bpf.te
> create mode 100644 policy/test_fdreceive_bpf.te
> create mode 100644 tests/bpf/.gitignore
> create mode 100644 tests/bpf/Makefile
> create mode 100644 tests/bpf/bpf_common.c
> create mode 100644 tests/bpf/bpf_common.h
> create mode 100644 tests/bpf/bpf_test.c
> create mode 100755 tests/bpf/test
>
prev parent reply other threads:[~2019-09-18 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 14:56 [PATCH V4 0/3] selinux-testsuite: Add BPF tests Richard Haines
2019-09-17 14:56 ` [PATCH V4 1/3] " Richard Haines
2019-09-18 14:58 ` Stephen Smalley
2019-09-19 13:36 ` Richard Haines
2019-09-17 14:56 ` [PATCH V4 2/3] selinux-testsuite: Add BPF support to fdreceive test Richard Haines
2019-09-18 15:12 ` Stephen Smalley
2019-09-19 13:41 ` Richard Haines
2019-09-17 14:56 ` [PATCH V4 3/3] selinux-testsuite: Add BPF support to binder test Richard Haines
2019-09-18 15:41 ` Stephen Smalley [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=a43a310c-346e-60b8-bf45-9c7663e73c89@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=paul@paul-moore.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@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).