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 16:42:39 -0700 [thread overview]
Message-ID: <20081004164239.0c1483a4@infradead.org> (raw)
In-Reply-To: <20081004220220.GK10632@outflux.net>
On Sat, 4 Oct 2008 15:02:20 -0700
Kees Cook <kees.cook@canonical.com> wrote:
> On Sat, Oct 04, 2008 at 02:51:49PM -0700, Arjan van de Ven wrote:
> > 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.
>
> Nothing else seemed appropriate, but I could make a brand new proc
> file, if that's sensible. "status_private" ?
how about a file called "personality" that has each set bit as an ascii
version ?
(one per line maybe)
--
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 23:43 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 [this message]
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
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=20081004164239.0c1483a4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox