From: "Christian Göttsche" <cgzones@googlemail.com>
To: selinux@vger.kernel.org
Cc: bpf@vger.kernel.org
Subject: [PATCH v4 0/9] Introduce capable_any()
Date: Thu, 11 May 2023 16:25:33 +0200 [thread overview]
Message-ID: <20230511142535.732324-10-cgzones@googlemail.com> (raw)
In-Reply-To: <20230511142535.732324-1-cgzones@googlemail.com>
Add the interfaces `capable_any()` and `ns_capable_any()` as an
alternative to multiple `capable()`/`ns_capable()` calls, like
`capable_any(CAP_SYS_NICE, CAP_SYS_ADMIN)` instead of
`capable(CAP_SYS_NICE) || capable(CAP_SYS_ADMIN)`.
`capable_any()`/`ns_capable_any()` will in particular generate exactly
one audit message, either for the left most capability in effect or, if
the task has none, the first one.
This is especially helpful with regard to SELinux, where each audit
message about a not allowed capability request will create a denial
message. Using this new wrapper with the least invasive capability as
left most argument (e.g. CAP_SYS_NICE before CAP_SYS_ADMIN) enables
policy writers to only grant the least invasive one for the particular
subject instead of both.
v3 discussion:
https://patchwork.kernel.org/project/selinux/patch/20220615152623.311223-8-cgzones@googlemail.com/
v4:
- add CAP_OPT_NODENYAUDIT capable flag
Christian Göttsche (9):
capability: introduce new capable flag NODENYAUDIT
capability: add any wrapper to test for multiple caps with exactly one
audit message
capability: use new capable_any functionality
block: use new capable_any functionality
drivers: use new capable_any functionality
fs: use new capable_any functionality
kernel: use new capable_any functionality
bpf: use new capable_any functionality
net: use new capable_any functionality
block/ioprio.c | 9 +--
drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 3 +-
drivers/net/caif/caif_serial.c | 2 +-
drivers/s390/block/dasd_eckd.c | 2 +-
fs/pipe.c | 2 +-
include/linux/capability.h | 17 ++++--
include/linux/security.h | 2 +
include/net/sock.h | 1 +
kernel/bpf/syscall.c | 2 +-
kernel/capability.c | 70 ++++++++++++++++++++++++
kernel/fork.c | 2 +-
net/caif/caif_socket.c | 2 +-
net/core/sock.c | 18 +++---
net/ieee802154/socket.c | 6 +-
net/ipv4/ip_sockglue.c | 4 +-
net/ipv6/ipv6_sockglue.c | 3 +-
net/unix/scm.c | 2 +-
security/apparmor/capability.c | 8 ++-
security/selinux/hooks.c | 14 +++--
19 files changed, 123 insertions(+), 46 deletions(-)
--
2.40.1
next prev parent reply other threads:[~2023-05-11 14:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 14:25 [PATCH v4 1/9] capability: introduce new capable flag NODENYAUDIT Christian Göttsche
2023-05-11 14:25 ` [PATCH v4 2/9] capability: add any wrapper to test for multiple caps with exactly one audit message Christian Göttsche
2023-05-11 14:25 ` [PATCH v4 3/9] capability: use new capable_any functionality Christian Göttsche
2023-05-16 18:42 ` Andrii Nakryiko
2023-05-11 14:25 ` [PATCH v4 4/9] block: " Christian Göttsche
2023-05-11 15:35 ` Christoph Hellwig
2023-05-11 16:53 ` Christian Göttsche
2023-05-11 14:25 ` [PATCH v4 5/9] drivers: " Christian Göttsche
2023-05-11 14:25 ` Christian Göttsche
2023-05-11 14:25 ` Christian Göttsche
2023-05-16 6:33 ` Alexander Gordeev
2023-05-16 6:33 ` Alexander Gordeev
2023-05-16 6:33 ` Alexander Gordeev
2023-05-11 14:25 ` [PATCH v4 6/9] fs: " Christian Göttsche
2023-05-15 7:56 ` Christian Brauner
2023-05-11 14:25 ` [PATCH v4 7/9] kernel: " Christian Göttsche
2023-05-15 7:54 ` Christian Brauner
2023-05-11 14:25 ` [PATCH v4 8/9] bpf: " Christian Göttsche
2023-05-16 18:42 ` Andrii Nakryiko
2023-05-11 14:25 ` [PATCH v4 9/9] net: " Christian Göttsche
2023-05-22 13:56 ` Miquel Raynal
2023-05-11 14:25 ` Christian Göttsche [this message]
2023-05-31 14:07 ` [PATCH v4 1/9] capability: introduce new capable flag NODENYAUDIT Serge E. Hallyn
2023-05-31 14:08 ` Serge E. Hallyn
2023-05-31 18:34 ` Christian Göttsche
2023-05-31 22:13 ` Paul Moore
2023-06-06 19:00 ` Serge E. Hallyn
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=20230511142535.732324-10-cgzones@googlemail.com \
--to=cgzones@googlemail.com \
--cc=bpf@vger.kernel.org \
--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 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.