linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mickaël Salaün" <mic@digikod.net>
To: Christian Brauner <christian.brauner@ubuntu.com>,
	Jann Horn <jannh@google.com>, Kees Cook <keescook@chromium.org>,
	Oleg Nesterov <oleg@redhat.com>
Cc: "Mickaël Salaün" <mic@digikod.net>,
	"Eric Paris" <eparis@redhat.com>,
	"James Morris" <jmorris@namei.org>,
	"Serge E . Hallyn" <serge@hallyn.com>,
	"Tyler Hicks" <tyhicks@linux.microsoft.com>,
	"Will Drewry" <wad@chromium.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH v1 0/2] Fix misuse of security_capable()
Date: Fri, 30 Oct 2020 13:38:47 +0100	[thread overview]
Message-ID: <20201030123849.770769-1-mic@digikod.net> (raw)

This series replaces all the use of security_capable(current_cred(),
...) with ns_capable{,_noaudit}() which set PF_SUPERPRIV.

This initially come from a review of Landlock by Jann Horn:
https://lore.kernel.org/lkml/CAG48ez1FQVkt78129WozBwFbVhAPyAr9oJAHFHAbbNxEBr9h1g@mail.gmail.com/

Mickaël Salaün (2):
  ptrace: Set PF_SUPERPRIV when checking capability
  seccomp: Set PF_SUPERPRIV when checking capability

 kernel/ptrace.c  | 18 ++++++------------
 kernel/seccomp.c |  5 ++---
 2 files changed, 8 insertions(+), 15 deletions(-)


base-commit: 3650b228f83adda7e5ee532e2b90429c03f7b9ec
-- 
2.28.0


             reply	other threads:[~2020-10-30 12:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 12:38 Mickaël Salaün [this message]
2020-10-30 12:38 ` [PATCH v1 1/2] ptrace: Set PF_SUPERPRIV when checking capability Mickaël Salaün
2020-10-30 15:47   ` Jann Horn
2020-10-30 16:06     ` Mickaël Salaün
2020-10-30 18:00       ` Jann Horn
2020-10-30 12:38 ` [PATCH v1 2/2] seccomp: " Mickaël Salaün
2020-10-30 15:34   ` Jann Horn
2020-11-17 21:08 ` [PATCH v1 0/2] Fix misuse of security_capable() Kees Cook

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=20201030123849.770769-1-mic@digikod.net \
    --to=mic@digikod.net \
    --cc=christian.brauner@ubuntu.com \
    --cc=eparis@redhat.com \
    --cc=jannh@google.com \
    --cc=jmorris@namei.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=serge@hallyn.com \
    --cc=stable@vger.kernel.org \
    --cc=tyhicks@linux.microsoft.com \
    --cc=wad@chromium.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).