From owner-freebsd-security  Tue Feb 18 23:15:28 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA09092
          for security-outgoing; Tue, 18 Feb 1997 23:15:28 -0800 (PST)
Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [163.195.220.170])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09083
          for <security@freebsd.org>; Tue, 18 Feb 1997 23:15:23 -0800 (PST)
Received: (from rbezuide@localhost)
	by oskar.nanoteq.co.za (8.8.5/8.8.5) id JAA22361;
	Wed, 19 Feb 1997 09:14:38 +0200 (SAT)
From: Reinier Bezuidenhout <rbezuide@oskar.nanoteq.co.za>
Message-Id: <199702190714.JAA22361@oskar.nanoteq.co.za>
Subject: Re: Coredumps and setuids .. interesting..
In-Reply-To: <199702190649.WAA16181@saguaro.flyingfox.com> from Jim Shankland at "Feb 18, 97 10:49:22 pm"
To: jas@flyingfox.COM (Jim Shankland)
Date: Wed, 19 Feb 1997 09:14:38 +0200 (SAT)
Cc: security@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> David Greenman writes, re coredumping setuid processes:
> 
> > Hmmm. Either my replies aren't getting through to bugtraq, or
> > people are just ignoring them. As of FreeBSD 2.1.6 and newer
> > versions, we don't core dump for setuid processes. It's been
> > this way for nearly a year in -current, but the change didn't
> > get merged into the 2.1.x branch until after the 2.1.5
> > release...that was an oversight.

This is weird ... I have a 2.1.0 machine that I upgraded to a
2.1.6.1 machine just before 2.1.6 was "freezed".  I tried the
rlogin coredump thingy and it did work.  I could see ALL the
users AND their passwords :/

> And I tried it out on an old laptop that still has 2.1.0-951104-SNAP,
> and it wouldn't dump the core of a setuid process.  (I don't have
> a 2.1.5 system to try it out on.)

Then it gor broke somewhere again ?


Reinier