From: Andy Isaacson <adi@hexapodia.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Kees Cook <kees@outflux.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: maps protection
Date: Fri, 9 Mar 2007 17:37:36 -0800 [thread overview]
Message-ID: <20070310013736.GA18877@hexapodia.org> (raw)
In-Reply-To: <1173241331.3236.10.camel@laptopd505.fenrus.org>
On Tue, Mar 06, 2007 at 08:22:11PM -0800, Arjan van de Ven wrote:
> > How about using a reduced check, as is done for fd and environ? This
> > would allow root-running system monitors to still do their job.
> > Effectively, this changes the test from "is ptracing" to just "can
> > ptrace".
> >
> > If this still isn't considered safe, I'll add the maps_protect file...
>
> btw I consider it an information leak that any user can see which
> files/libraries any other user and root has mmap'd. (and with glibc's
> stdio mmap feature that goes even beyond direct mmap to fopen()'d).
>
> If root or some other user wants to watch
> hillary-vs-obama-in-the-mud.avi, no other user has ANY business even
> seeing that. So at minimum it's a privacy issue showing the filenames...
Sure, I would be fine with making /proc/<pid>/maps mode 0400 (so long as
root can still read it). But please don't take away my ability to debug
applications using pmap(1). It's so incredibly useful to be able to say
"ah, look, he mapped nss_nis.so rather than nss_nisplus.so".
-andy
next prev parent reply other threads:[~2007-03-10 1:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070307012234.GN9621@outflux.net>
[not found] ` <20070306175609.267bd7a9.akpm@linux-foundation.org>
[not found] ` <20070307021335.GR9621@outflux.net>
[not found] ` <20070306185942.585e7cd1.akpm@linux-foundation.org>
2007-03-07 3:14 ` [PATCH] proc: maps protection Kees Cook
2007-03-07 4:22 ` Arjan van de Ven
2007-03-08 20:55 ` Kees Cook
2007-03-10 2:30 ` Andrew Morton
2007-03-10 5:01 ` Arjan van de Ven
2007-03-10 18:33 ` Kees Cook
2007-03-11 0:21 ` Andrew Morton
2007-03-11 0:55 ` Matt Mackall
2007-03-11 1:43 ` Kees Cook
2007-03-11 1:55 ` Kees Cook
2007-03-12 17:20 ` [PATCH] getrusage() : Fill ru_inblock and ru_oublock fields if possible Eric Dumazet
2007-03-10 1:37 ` Andy Isaacson [this message]
2007-03-05 20:15 [PATCH] proc: maps protection Kees Cook
2007-03-06 0:23 ` Kees Cook
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=20070310013736.GA18877@hexapodia.org \
--to=adi@hexapodia.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=kees@outflux.net \
--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