From owner-freebsd-current Thu Oct 31 10:31:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26274 for current-outgoing; Thu, 31 Oct 1996 10:31:51 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA26269 for ; Thu, 31 Oct 1996 10:31:48 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA25640; Thu, 31 Oct 1996 11:23:33 -0700 From: Terry Lambert Message-Id: <199610311823.LAA25640@phaeton.artisoft.com> Subject: Re: /var/mail (was: re: Help, permission problems...) To: scrappy@ki.net (Marc G. Fournier) Date: Thu, 31 Oct 1996 11:23:32 -0700 (MST) Cc: terry@lambert.org, wollman@lcs.mit.edu, jgreco@brasil.moneng.mei.com, current@freebsd.org In-Reply-To: from "Marc G. Fournier" at Oct 31, 96 01:05:30 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > 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. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.