mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Petr Baudis <pasky@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Let even non-dumpable tasks access /proc/self/fd
Date: Fri, 9 Jun 2006 12:01:42 -0500	[thread overview]
Message-ID: <20060609170142.GA23990@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20060606233820.GL28014@pasky.or.cz>

Quoting Petr Baudis (pasky@suse.cz):
> This kernel patch fixes the problem by letting the process access its
> own /proc/self/fd - as far as I can see, this should be reasonably safe
> since for the process, this does not reveal "anything new". Feel free to
> comment on this.

Given that

	fd=open("/etc/shadow", "r");
	setuid(1000);
	read(fd, buf, 100);

is possible before this patch, I agree - nothing new is revealed with
this patch  :)

(I've been waiting to respond because it does make me nervous, but
it seems clear that is unwarranted)

thanks,
-serge

      reply	other threads:[~2006-06-09 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 23:38 Petr Baudis
2006-06-09 17:01 ` Serge E. Hallyn [this message]

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=20060609170142.GA23990@sergelap.austin.ibm.com \
    --to=serue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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®