Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site lsuc.UUCP Path: utzoo!lsuc!dave From: dave@lsuc.UUCP (David Sherman) Newsgroups: net.bugs.uucp Subject: Re: Read permission on /etc/phones Message-ID: <696@lsuc.UUCP> Date: Sun, 7-Jul-85 06:45:59 EDT Article-I.D.: lsuc.696 Posted: Sun Jul 7 06:45:59 1985 Date-Received: Sun, 7-Jul-85 07:32:35 EDT References: <472@qantel.UUCP> <170@motel6.UUCP> <> <154@telesoft.UUCP> Reply-To: dave@lsuc.UUCP (David Sherman) Organization: Law Society of Upper Canada, Toronto Lines: 18 Keywords: tip, uucp, LCK Summary: just write a simple LCK remover In article <154@telesoft.UUCP> pilotti@telesoft.UUCP (Keith Pilotti @shine) writes: || `tip' creates the LCK file while SUID, and no longer has write || permission in /usr/spool/uucp once it changes the UID. The LCK || file therefore remains. || || For binary sites the only "solution" seems to be to leave this || directory writable. Yuck. Why not just write a simple set-UID program which removes the LCK file and nothing else? You can get fancy with various checks, of course, but in its simplest form it's a one-line C program. Dave Sherman The Law Society of Upper Canada Toronto -- { ihnp4!utzoo pesnta utcs hcr decvax!utcsri } !lsuc!dave