From owner-freebsd-security Wed Jun 7 6:53:31 2000 Delivered-To: freebsd-security@freebsd.org Received: from borderware.com (gateway.borderware.com [207.236.65.226]) by hub.freebsd.org (Postfix) with ESMTP id A359337BCBB for ; Wed, 7 Jun 2000 06:53:13 -0700 (PDT) (envelope-from bmw@borderware.com) Received: by gateway.borderware.com id <117121>; Wed, 7 Jun 2000 09:51:18 -0400 From: "Bruce M. Walker" Message-Id: <00Jun7.095118edt.117121@gateway.borderware.com> Subject: Re: FreeBSDDEATH.c.txt (mmap dirty page no check bug) In-Reply-To: <200006071311.e57DBsW08744@cwsys.cwsent.com> from Cy Schubert - ITSD Open Systems Group at "Jun 7, 2000 06:11:09 am" To: freebsd-security@FreeBSD.ORG Date: Wed, 7 Jun 2000 09:53:05 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Cy Schubert - ITSD Open Systems Group wrote: > Replacement candidates for /tmp and /var/tmp are: > > 1. Each user has a subdirectory in /tmp as /tmp/$USER. An idea brought > forth to BUGTRAQ by Theo de Raadt of the OpenBSD project. > > 2. Each user maintains their own /tmp as $HOME/tmp or some such thing. > An idea I had discussed with my co-workers a number of years ago. #1 I'll buy into. I have actually implemented that for an HPUX-based MIS system using a Progress db. All users have their own "playpen" and cron sweeps up the all-too-frequent cores and printer temps. #2 is *not* going to cut it when the user homes are NFS-mounted from a central server(s). On the other hand, it's a good idea when the server has more resources than the workstation (terabyte FC-disks over gigabit ether). Is this topic not drifting away from being strictly "freebsd-security"? -bmw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message