From: Arjan van de Ven <arjan@infradead.org>
To: Kees Cook <kees.cook@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: add "personality" to process status file
Date: Sat, 4 Oct 2008 14:51:49 -0700 [thread overview]
Message-ID: <20081004145149.52c34ee7@infradead.org> (raw)
In-Reply-To: <20081002211424.GJ10632@outflux.net>
On Thu, 2 Oct 2008 14:14:24 -0700
Kees Cook <kees.cook@canonical.com> wrote:
> There is no sane way to query the personality flags of arbitrary
> process from userspace. This adds the flags to the /proc/$pid/status
> file. For example, to detect READ_IMPLIES_EXEC:
>
.. I'm sure local exploit writers will love this to find out which
processes to attack.
Realistically, this probably shouldn't be in a world-readable file.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-10-04 21:52 UTC|newest]
Thread overview: 18+ 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 [this message]
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
[not found] ` <20081005101438.GR10632-oSa+0FWJbaXR7s880joybQ@public.gmane.org>
2008-10-07 13:39 ` Michael Kerrisk
2008-10-07 13:39 ` 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
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=20081004145149.52c34ee7@infradead.org \
--to=arjan@infradead.org \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.