From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] SELinux fixes for v4.20 (#2)
Date: Thu, 29 Nov 2018 11:48:40 -0500 [thread overview]
Message-ID: <CAHC9VhTvN5iQkqDXsKuqwr73_eHwi6-0khVRb-pWQa439rN+3g@mail.gmail.com> (raw)
Hi Linus,
One more SELinux fix for v4.20: add some missing netlink message to
SELinux permission mappings. The netlink messages were added in
v4.19, but unfortunately we didn't catch it then because the mechanism
to catch these things was bypassed. In addition to adding the
mappings, we're adding some comments to the code to hopefully prevent
bypasses in the future.
Please merge for the next v4.20-rc release, thanks.
-Paul
--
The following changes since commit 877181a8d9dc663f7a73f77f50af714d7888ec3b:
selinux: fix non-MLS handling in mls_context_to_sid()
(2018-11-13 21:44:33 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20181129
for you to fetch changes up to 598e1a42e9626213565d3b22ea948ce78556512a:
selinux: add support for RTM_NEWCHAIN, RTM_DELCHAIN, and RTM_GETCHAIN
(2018-11-29 11:32:02 -0500)
----------------------------------------------------------------
selinux/stable-4.20 PR 20181129
----------------------------------------------------------------
Paul Moore (1):
selinux: add support for RTM_NEWCHAIN, RTM_DELCHAIN, and RTM_GETCHAIN
security/selinux/nlmsgtab.c | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
--
paul moore
www.paul-moore.com
next reply other threads:[~2018-11-29 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 16:48 Paul Moore [this message]
2018-11-29 23:10 ` [GIT PULL] SELinux fixes for v4.20 (#2) pr-tracker-bot
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=CAHC9VhTvN5iQkqDXsKuqwr73_eHwi6-0khVRb-pWQa439rN+3g@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@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 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).