From owner-freebsd-current  Wed May 14 13:55:22 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA04215
          for current-outgoing; Wed, 14 May 1997 13:55:22 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA04210
          for <current@freebsd.org>; Wed, 14 May 1997 13:55:19 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA28492; Wed, 14 May 1997 14:55:12 -0600 (MDT)
Date: Wed, 14 May 1997 14:55:12 -0600 (MDT)
Message-Id: <199705142055.OAA28492@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: Nate Williams <nate@mt.sri.com>,
        joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), current@freebsd.org
Subject: Re: RELENG_2_2 
In-Reply-To: <17372.863642768@time.cdrom.com>
References: <199705141614.KAA27066@rocky.mt.sri.com>
	<17372.863642768@time.cdrom.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > Making us work with vendors is *less* important than opening FreeBSD up
> > for security holes.  Go re-read all of the arguements for/against the
> 
> I'm still waiting for someone to explain to me how this change opens
> FreeBSD up to anything - all I see is a lot of scare-mongering but
> no technical "meat" in this argument.

See below, and go re-read all of the arguments again (which you've
seemed to have ignored).

> 
> > Now you're just being silly and ignoring the fact that you've changed
> > (and probably broken) the way mail is handled in stock FreeBSD if people
> 
> "Probably" - you're going to have to do better than that.

Mail locking, as already been said *many* times.  However, depending on
usage, it may not bite anyone, or then again it might.  It's kind of
like serving your mail spool over NFS, most of the time it works, but
sometimes it totally corrupts your mbox.

That's the primary reason, although there are also other minor problems
as well.




Nate