Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!ut-sally!bcm!watson!sob
From: sob@watson.tmc.edu (Stan Barber)
Newsgroups: comp.sources.d
Subject: Re: kermit lock files - setuid/setgid security holes
Message-ID: <397@uni2.bcm.tmc.edu>
Date: Thu, 20-Aug-87 17:26:17 EDT
Article-I.D.: uni2.397
Posted: Thu Aug 20 17:26:17 1987
Date-Received: Sat, 22-Aug-87 12:04:05 EDT
References: <605@quacky.UUCP>
Sender: usenet@bcm.tmc.edu
Reply-To: sob@watson.bcm.tmc.edu (Stan Barber)
Distribution: world
Organization: Baylor College of Medicine, Houston, Tx
Lines: 8

I should point out that C-Kermit(041) does handle lock files correctly
under BSD4.3 with the 4.3UUCP locking structure. This creates a lock
directory (/usr/spool/uucp/LCK) that is publically writable and each
program (except kermit) using the locking protocol is smart enough to test for
dead locks (coming from programs that aborted and did not remove its
lock).

Stan