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

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.

I was thinking I'd follow up with a patch to make things
a bit more logical as far as info exposure goes. It makes
no sense to have the /proc/*/exe link fail a readlink()
when one can reliably guess that data from elsewhere.

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)

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

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22  9:50 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 [this message]
2006-01-22 19:44     ` Arjan van de Ven
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=787b0d920601221117l78a92fd1udc8601068dbde42c@mail.gmail.com \
    --to=acahalan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.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

all inboxes | Powered by JetHome®