From owner-freebsd-security Fri Jun 7 14:48:16 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25564 for security-outgoing; Fri, 7 Jun 1996 14:48:16 -0700 (PDT) Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA25554 for ; Fri, 7 Jun 1996 14:48:11 -0700 (PDT) Received: from venus.mcs.com (root@Venus.mcs.com [192.160.127.92]) by kitten.mcs.com (8.7.5/8.6.9) with SMTP id QAA16627; Fri, 7 Jun 1996 16:48:02 -0500 (CDT) Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Fri, 7 Jun 96 16:48 CDT Message-Id: Subject: Re: FreeBSD's /var/mail permissions To: pst@shockwave.com (Paul Traina) Date: Fri, 7 Jun 1996 16:48:01 -0500 (CDT) From: "Karl Denninger, MCSNet" Cc: nate@sri.MT.net, softweyr@xmission.com, security@FreeBSD.org In-Reply-To: <199606072105.OAA00533@precipice.shockwave.com> from "Paul Traina" at Jun 7, 96 02:05:23 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-security@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Mail locking, to be effective, must be soley performed through the use of > the flock() call on the mail file itself. > > Locking schemes relying on other mechanisms are not effective. > > Sorry. Mail locking, to be effective, must *work across machines* so that NFS mounts of the mail directory work. flock() cannot be trusted to work in this environment, and in fact doesn't even attempt to work on FreeBSD. Does this mean we should give up on using mail? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity Modem: [+1 312 248-0900] | T1 from $600 monthly; speeds to DS-3 available Voice: [+1 312 803-MCS1] | 21 Chicagoland POPs, ISDN, 28.8, much more Fax: [+1 312 248-9865] | Email to "info@mcs.net" WWW: http://www.mcs.net/ ISDN - Get it here TODAY! | Home of Chicago's only FULL Clarinet feed!