From owner-freebsd-current Thu Oct 31 12:58:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA07142 for current-outgoing; Thu, 31 Oct 1996 12:58:39 -0800 (PST) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA07123 for ; Thu, 31 Oct 1996 12:58:22 -0800 (PST) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.8.2/8.7.5) with SMTP id PAA09984; Thu, 31 Oct 1996 15:56:19 -0500 (EST) Date: Thu, 31 Oct 1996 15:56:18 -0500 (EST) From: "Marc G. Fournier" To: Terry Lambert cc: wollman@lcs.mit.edu, jgreco@brasil.moneng.mei.com, current@freebsd.org Subject: Re: /var/mail (was: re: Help, permission problems...) In-Reply-To: <199610311823.LAA25640@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 31 Oct 1996, Terry Lambert wrote: > > > He is also the principle author (apparently) of IMAP4, a highly > > > desirable piece of software for anyone with a 1995 or later mail > > > client. > > Agreed...which is why I brought this whole discussion into here... > > > > From what Mark has said, about the only way I can think of for > > getting this *obvious* security bug fixed is to, either: > > [ ... ] > > > IMHO...what having .lock locking capabilities in IMAP4 is > > doing is encouraging system administrators to use NFS mounted mail > > spools, instead of *teaching* system administrators to *not* setup > > their systems that way... > > Or publicize the denial of service attack in the news groups where > IMAP4 is discussed and hope someone uses it. > Very nasty :) Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org