From owner-freebsd-security  Fri Jun  7 15:35:27 1996
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA29903
          for security-outgoing; Fri, 7 Jun 1996 15:35:27 -0700 (PDT)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA29890
          for <security@freebsd.org>; Fri, 7 Jun 1996 15:35:24 -0700 (PDT)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id QAA01040; Fri, 7 Jun 1996 16:35:15 -0600
Date: Fri, 7 Jun 1996 16:35:15 -0600
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199606072235.QAA01040@rocky.sri.MT.net>
To: Paul Traina <pst@shockwave.com>
Cc: Nate Williams <nate@sri.MT.net>, Barnacle Wes <softweyr@xmission.com>,
        security@freebsd.org
Subject: Re: FreeBSD's /var/mail permissions 
In-Reply-To: <199606072234.PAA00814@precipice.shockwave.com>
References: <199606072107.PAA00612@rocky.sri.MT.net>
	<199606072234.PAA00814@precipice.shockwave.com>
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Their locking systems are irrelevant if they do not cooperate with
> mail.local.

See PHK's recent email.  Renaming the file to something else (in
/var/mail) is a *real* effective way of making sure you lock the
file. :)


Nate