From: Alan Cox <alan@redhat.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Alan Cox <alan@redhat.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org, torvalds@osdl.org
Subject: Re: Patch for comment: setuid core dumps
Date: Mon, 27 Sep 2004 17:10:11 -0400 [thread overview]
Message-ID: <20040927211011.GA15168@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040927140353.Z1973@build.pdx.osdl.net>
On Mon, Sep 27, 2004 at 02:03:53PM -0700, Chris Wright wrote:
> > +2 - (suidsafe) - any binary which normally not be dumped is dumped
> > + readable by root only. This allows the end user to remove
> > + such a dump but not access it directly. For security reasons
> > + core dumps in this mode will not overwrite one another or
> > + other files. This mode is appropriate when adminstrators are
> > + attempting to debug problems in a normal environment.
> > +
>
> But, in general, did you double check how this plays with /proc
> (task_dumpable) and ptrace_attach type stuff? That seems sketchy.
I reviewed it in terms of ptrace. I'll review the /proc stuff in detail. I'd
not given that anything like sufficient thought.
prev parent reply other threads:[~2004-09-27 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 20:26 Patch for comment: setuid core dumps Alan Cox
2004-09-27 20:37 ` Randy.Dunlap
2004-09-27 21:03 ` Chris Wright
2004-09-27 21:10 ` Alan Cox [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=20040927211011.GA15168@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.