From: "Michael Kerrisk" <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Kees Cook <kees.cook-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: Alexey Dobriyan
<adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Arjan van de Ven <arjan-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] proc: show personality via /proc/pid/personality
Date: Wed, 8 Oct 2008 04:45:22 +0200 [thread overview]
Message-ID: <cfd18e0f0810071945j4ebbe366qdf2e98fe3d0306eb@mail.gmail.com> (raw)
In-Reply-To: <20081007161422.GD10357-oSa+0FWJbaXR7s880joybQ@public.gmane.org>
Hi Kees,
On Tue, Oct 7, 2008 at 6:14 PM, Kees Cook <kees.cook-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org> wrote:
> 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-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org> 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-u79uwXL29TY76Z2rM5mHXA@public.gmane.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. :)
It's there, but only as of a few days ago.
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-10-08 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081002211424.GJ10632@outflux.net>
[not found] ` <20081004145149.52c34ee7@infradead.org>
[not found] ` <20081004220220.GK10632@outflux.net>
[not found] ` <20081004164239.0c1483a4@infradead.org>
[not found] ` <20081005004233.GL10632@outflux.net>
[not found] ` <20081004174843.6fe48a8e@infradead.org>
[not found] ` <20081005091120.GA21003@x200.localdomain>
[not found] ` <20081005101438.GR10632@outflux.net>
[not found] ` <20081005101438.GR10632-oSa+0FWJbaXR7s880joybQ@public.gmane.org>
2008-10-07 13:39 ` [PATCH v2] proc: show personality via /proc/pid/personality Michael Kerrisk
2008-10-07 16:14 ` Kees Cook
[not found] ` <20081007161422.GD10357-oSa+0FWJbaXR7s880joybQ@public.gmane.org>
2008-10-08 2:45 ` Michael Kerrisk [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=cfd18e0f0810071945j4ebbe366qdf2e98fe3d0306eb@mail.gmail.com \
--to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=arjan-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=kees.cook-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).