From owner-freebsd-hackers Sun Oct 20 01:01:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA14935 for hackers-outgoing; Sun, 20 Oct 1996 01:01:35 -0700 (PDT) Received: from critter.tfs.com (disn1.cybercity.dk [194.16.57.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA14926; Sun, 20 Oct 1996 01:01:28 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id KAA22932; Sun, 20 Oct 1996 10:01:25 +0200 (MET DST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: tech-userlevel@NetBSD.ORG, freebsd-hackers@freefall.freebsd.org Subject: Re: setuid, core dumps, ftpd, and DB In-reply-to: Your message of "Sun, 20 Oct 1996 09:41:39 +0200." <199610200741.JAA27953@uriah.heep.sax.de> Date: Sun, 20 Oct 1996 10:01:24 +0200 Message-ID: <22930.845798484@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199610200741.JAA27953@uriah.heep.sax.de>, J Wunsch writes: >As Poul-Henning Kamp wrote: > >> It was pointed out by me already 8 years ago: >> >> "[...] core-dumps as default is an evil thing. There should be >> some way to >enable< core-dumps when you want them, rather than >> have them as default. This would also solve security issue >> where a core-dump may contain sensitive information. [...]" >> >> What we need is really a new syscall: >> >> procctl(pid, function, arg) > >The only problem with this is that programs tend to dump core without >asking the developer first. ;-) That's the nature of bugs, the >programmer often does not anticipate them. Thus, they are sometimes a >good means for a post-mortem analysis. I suppose most people would have the system-wide default be "core-dumps on" -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.