From: Micah Morton <mortonm@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: [GIT PULL] SafeSetID LSM changes for v5.8
Date: Tue, 9 Jun 2020 11:26:39 -0700 [thread overview]
Message-ID: <CAJ-EccOy4qDpbfrP5=KH40LSOx1F4-ciY2=hFv_c+goUHLJ6PQ@mail.gmail.com> (raw)
The following changes since commit 3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162:
Linux 5.7 (2020-05-31 16:49:15 -0700)
are available in the Git repository at:
https://github.com/micah-morton/linux.git tags/LSM-add-setgid-hook-5.8
for you to fetch changes up to 04d244bcf92f525011e3df34b21fc39b0591ba93:
security: Add LSM hooks to set*gid syscalls (2020-06-09 10:22:13 -0700)
----------------------------------------------------------------
Add additional LSM hooks for SafeSetID
SafeSetID is capable of making allow/deny decisions for set*uid calls
on a system, and we want to add similar functionality for set*gid
calls. The work to do that is not yet complete, so probably won't make
it in for v5.8, but we are looking to get this simple patch in for
v5.8 since we have it ready. We are planning on the rest of the work
for extending the SafeSetID LSM being merged during the v5.9 merge
window.
This patch was sent to the security mailing list and there were no objections.
Signed-off-by: Micah Morton <mortonm@chromium.org>
----------------------------------------------------------------
Micah Morton (1):
security: Add LSM hooks to set*gid syscalls
include/linux/lsm_hook_defs.h | 2 ++
include/linux/lsm_hooks.h | 9 +++++++++
include/linux/security.h | 9 +++++++++
kernel/sys.c | 15 ++++++++++++++-
security/security.c | 6 ++++++
5 files changed, 40 insertions(+), 1 deletion(-)
next reply other threads:[~2020-06-09 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 18:26 Micah Morton [this message]
2020-06-12 21:23 ` [GIT PULL] SafeSetID LSM changes for v5.8 Linus Torvalds
2020-06-14 18:03 ` Micah Morton
2020-06-14 18:39 ` Linus Torvalds
2020-06-14 19:12 ` Micah Morton
2020-06-14 19:20 ` Linus Torvalds
2020-06-15 16:28 ` Micah Morton
2020-06-14 18:55 ` pr-tracker-bot
2020-06-15 5:21 ` James Morris
2020-06-15 16:22 ` Micah Morton
2020-06-15 18:03 ` James Morris
2020-06-16 16:35 ` Micah Morton
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='CAJ-EccOy4qDpbfrP5=KH40LSOx1F4-ciY2=hFv_c+goUHLJ6PQ@mail.gmail.com' \
--to=mortonm@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.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.