From owner-freebsd-hackers Mon Oct 21 11:41:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA03028 for hackers-outgoing; Mon, 21 Oct 1996 11:41:08 -0700 (PDT) Received: from answerman.mindspring.com (answerman.mindspring.com [204.180.128.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA03023 for ; Mon, 21 Oct 1996 11:41:01 -0700 (PDT) Received: from bogus.mindspring.com (borg.mindspring.com [204.180.128.14]) by answerman.mindspring.com (8.7.5/8.7.3) with SMTP id OAA08474; Mon, 21 Oct 1996 14:37:59 -0400 (EDT) Message-Id: <1.5.4.32.19961021183752.0086ea30@mindspring.com> X-Sender: kpneal@mindspring.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 21 Oct 1996 14:37:52 -0400 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: "Kevin P. Neal" Subject: Re: setuid, core dumps, ftpd, and DB Cc: tech-userlevel@NetBSD.ORG, freebsd-hackers@freebsd.org (FreeBSD hackers) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 09:58 AM 10/20/96 +0200, J Wunsch wrote: >As Chris G Demetriou wrote: > >> Charles, re: "is a core dump on this weird file system safe"? >> Actually, a good solution there might be a "NOCOREDUMP" mount flag, a >> la NOSUID and NOEXEC. That has several advantages: > >It doesn't solve the problem where this discussion originated, but i >like this idea. I've seen programs dump 80 MB core files over >ethernet -- and once they do this, you cannot stop them. (Maybe you >could quickly delete the file from the server, so the client would get >a stale NFS file handle, but it's a crock.) Heck, early in the summer I caused a 180MB core file to be sent over NFS. Nobody from the helpdesk could log into the NFS server. The login server had an ugly load average, and a hung process that couldn't be kill -9'd. It sorted itself out, after a while, but tying up servers in a corporate environment is on the list of "bad things to do". Since I had just started work a month before, and had decided that I didn't like the way the shell and environment was set up, I set up my own. I didn't set the flag to limit the core file size until afterwards. It was a total accident. -- XCOMM Kevin P. Neal, Sophomore, Comp. Sci. \ kpneal@pobox.com XCOMM "Corrected!" -- Old Amiga tips file \ kpneal@eos.ncsu.edu XCOMM Visit the House of Retrocomputing: / Perm. Email: XCOMM http://www.pobox.com/~kpn/ / kevinneal@bix.com