From owner-freebsd-security Wed Jun 7 4:54:41 2000 Delivered-To: freebsd-security@freebsd.org Received: from jello.geekspace.com (216-064-051-142.inaddr.vitts.com [216.64.51.142]) by hub.freebsd.org (Postfix) with SMTP id 1EF9A37B738 for ; Wed, 7 Jun 2000 04:54:34 -0700 (PDT) (envelope-from psion@geekspace.com) Received: (qmail 694 invoked from network); 7 Jun 2000 11:57:36 -0000 Received: from nh050.inr.net (HELO geekspace.com) (216.64.66.50) by 216-064-051-142.inaddr.vitts.com with SMTP; 7 Jun 2000 11:57:36 -0000 Message-ID: <393E3710.363AC6CF@geekspace.com> Date: Wed, 07 Jun 2000 07:50:40 -0400 From: Chris Williams X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-security@FreeBSD.ORG Subject: Re: FreeBSDDEATH.c.txt (mmap dirty page no check bug) References: <200006070424.e574Od303232@cwsys.cwsent.com> <200006070655.XAA97086@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have to wonder, with all this discussion about one tmp being cleared at boot and the other not...Do FreeBSD users really reboot so often that this is an important case? ;) Isn't it kind of, well, short-sighted, to rely on cleaning something out at boot-time on a system which could potentailly see uptime measured in years? I would think it's even sillier to say that your security relies on /tmp being cleared at boot -- does that mean FreeBSD needs to be rebooted every x days to remain secure? Please. If this is the case, something is a lot more seriously wrong than having two /tmps.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message