Date: Mon, 27 Sep 2004 17:10:11 -0400
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
Message-ID: <20040927211011.GA15168@devserv.devel.redhat.com>
References: <20040927202616.GA22228@devserv.devel.redhat.com> <20040927140353.Z1973@build.pdx.osdl.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040927140353.Z1973@build.pdx.osdl.net>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 972
Lines: 19

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/