From: James Morris <jmorris@namei.org>
To: Will Drewry <wad@chromium.org>
Cc: Kees Cook <keescook@chromium.org>,
Andy Lutomirski <luto@amacapital.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-security-module@vger.kernel.org,
linux-arch@vger.kernel.org, linux-doc@vger.kernel.org,
kernel-hardening@lists.openwall.com, hpa@zytor.com,
mingo@redhat.com, peterz@infradead.org, tglx@linutronix.de,
Eric Paris <eparis@redhat.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
djm@mindrot.org, scarybeasts@gmail.com, indan@nul.nu,
pmoore@redhat.com, Jonathan Corbet <corbet@lwn.net>,
eric.dumazet@gmail.com, markus@chromium.org,
coreyb@linux.vnet.ibm.com, linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: Docs for PR_SET_NO_NEW_PRIVS
Date: Thu, 7 Jun 2012 11:29:48 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.2.02.1206071127340.12194@tundra.namei.org> (raw)
In-Reply-To: <CABqD9hYXKhX1=064DpbaBTAVd8-g43jKAPvtsbxEUTbgC1MPxg@mail.gmail.com>
On Tue, 5 Jun 2012, Will Drewry wrote:
> Or Documentation/prctl/no-new-privs.txt
>
> Just a decision between what it does and how you get to it, but I'd
> think either would make sense!
This makes sense as it's where the seccomp documentation is.
- James
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2012-06-07 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 17:04 Andy Lutomirski
2012-06-05 17:33 ` Kees Cook
2012-06-05 18:13 ` Will Drewry
2012-06-07 1:29 ` James Morris [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=alpine.LRH.2.02.1206071127340.12194@tundra.namei.org \
--to=jmorris@namei.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=coreyb@linux.vnet.ibm.com \
--cc=djm@mindrot.org \
--cc=eparis@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=hpa@zytor.com \
--cc=indan@nul.nu \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=markus@chromium.org \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=peterz@infradead.org \
--cc=pmoore@redhat.com \
--cc=scarybeasts@gmail.com \
--cc=serge.hallyn@canonical.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®