linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Albert Cahalan <acahalan@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] add /proc/*/pmap files
Date: Sun, 22 Jan 2006 20:44:19 +0100	[thread overview]
Message-ID: <1137959059.3328.45.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <787b0d920601221117l78a92fd1udc8601068dbde42c@mail.gmail.com>

On Sun, 2006-01-22 at 14:17 -0500, Albert Cahalan wrote:
> On 1/22/06, Arjan van de Ven <arjan@infradead.org> wrote:
> > On Sun, 2006-01-22 at 04:50 -0500, Albert Cahalan wrote:
> > > This adds a few things needed by the pmap command.
> > > They show up in /proc/*/pmap files.
> >
> >
> > also since this shows filenames and such, could you make the permissions
> > of the pmap file be 0400 ? (yes I know some others in the same dir
> > aren't 0400 yet, but I hope that that can be changed in the future,
> > adding more of these should be avoided for information-leak/exposure
> > reasons)
> 
> I thought it was the addresses you'd object to.

well both ;)

knowing that you're listening to Mrs Stefani's music rather than
watching her music clips is something you might not want to spread to
other users of your system. Or in other words, open files already
disclose "private" stuff. 

> I notice that Fedora Core 4 shipped with /proc/*/smaps
> files that were readable, but /proc/*/maps files that were
> not readable. (at least, a recent kernel update did)

that'd be a mistake


> As of now, I'm keeping mainstream kernel policy as is.

you're making a NEW file, so there is no "mainstream policy" yet. Please
do it right the first time so that it doesn't have to change later...



  reply	other threads:[~2006-01-22 19:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22  9:50 [PATCH] add /proc/*/pmap files Albert Cahalan
2006-01-22 10:03 ` Arjan van de Ven
2006-01-22 10:38   ` Kyle Moffett
2006-01-22 10:39 ` Willy Tarreau
2006-01-22 14:32 ` Jan Engelhardt
2006-01-22 20:02   ` Albert Cahalan
2006-01-22 14:36 ` Arjan van de Ven
2006-01-22 19:17   ` Albert Cahalan
2006-01-22 19:44     ` Arjan van de Ven [this message]
2006-01-22 19:58       ` Andrew Morton
2006-01-22 20:40         ` Albert Cahalan

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=1137959059.3328.45.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=acahalan@gmail.com \
    --cc=akpm@osdl.org \
    --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;
as well as URLs for NNTP newsgroup(s).