From: Kees Cook <kees.cook@canonical.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH v2] proc: show personality via /proc/pid/personality
Date: Tue, 7 Oct 2008 09:14:22 -0700 [thread overview]
Message-ID: <20081007161422.GD10357@outflux.net> (raw)
In-Reply-To: <517f3f820810070639q549ed2a1pe297e45108dfa007@mail.gmail.com>
Hi Michael,
On Tue, Oct 07, 2008 at 03:39:26PM +0200, Michael Kerrisk wrote:
> On Sun, Oct 5, 2008 at 12:14 PM, Kees Cook <kees.cook@canonical.com> wrote:
> > Make process personality flags visible in /proc. Since a process's
> > personality is potentially sensitive (e.g. READ_IMPLIES_EXEC), make this
> > file only readable by the process owner.
>
> Please CC userland interface changes to linux-api@vger.kernel.org
Sure, I'd be happy to do that for future stuff. I don't see this email
address mentioned anywhere in the kernel tree. It seems like this is
useful information that should go in either MAINTAINERS or better yet
Documentation/SubmittingPatches for it to be discoverable by future
patch-senders -- and somewhere that I can look it up easily later. :)
-Kees
--
Kees Cook
Ubuntu Security Team
next prev parent reply other threads:[~2008-10-07 16:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 21:14 [PATCH] proc: add "personality" to process status file Kees Cook
2008-10-02 22:46 ` Randy.Dunlap
2008-10-02 22:56 ` Kees Cook
2008-10-04 21:40 ` Alexey Dobriyan
2008-10-04 21:51 ` Arjan van de Ven
2008-10-04 22:02 ` Kees Cook
2008-10-04 23:42 ` Arjan van de Ven
2008-10-05 0:42 ` Kees Cook
2008-10-05 0:48 ` Arjan van de Ven
2008-10-05 9:11 ` Alexey Dobriyan
2008-10-05 10:07 ` Kees Cook
2008-10-05 10:14 ` [PATCH v2] proc: show personality via /proc/pid/personality Kees Cook
2008-10-05 23:20 ` Alexey Dobriyan
2008-10-07 13:39 ` Michael Kerrisk
2008-10-07 16:14 ` Kees Cook [this message]
2008-10-08 2:45 ` Michael Kerrisk
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=20081007161422.GD10357@outflux.net \
--to=kees.cook@canonical.com \
--cc=adobriyan@gmail.com \
--cc=arjan@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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