Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 exptools; site whuxl.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxr!mhuxt!houxm!whuxl!mike
From: mike@whuxl.UUCP (BALDWIN)
Newsgroups: net.unix-wizards
Subject: Re: Re: Another reason why - really /tmp
Message-ID: <715@whuxl.UUCP>
Date: Wed, 25-Sep-85 10:46:09 EDT
Article-I.D.: whuxl.715
Posted: Wed Sep 25 10:46:09 1985
Date-Received: Fri, 27-Sep-85 04:09:57 EDT
References: <1149@brl-tgr.ARPA> <182@graffiti.UUCP> <764@rlgvax.UUCP> <2279@sunybcs.UUCP>
Organization: AT&T Bell Laboratories, Whippany
Lines: 16

> > /tmp is world writeable.  This means that anyone can unlink tmp files. 
> > In particular, my application wants to pass state data from a child
> > process to a parent prodcess via a tmp file that the child creates,
> > and there are windows of vulnerability in this scheme, due to the unlink
> > trouble.
> 
> Easy.  have your application make a subdirectory in /tmp, and then place
> a file within that subdir.  As long as your subdirectory is not world
> writeable, you can place tmp files there w/o having a window of vulnerability.

But anyone can still move the directory in /tmp, and put another one
in its place.  The problem is still there.
-- 
			 / These are \		Michael Baldwin
			|  only >my<  |		AT&T Bell Labs
			 \ opinions. /		{at&t}!whuxl!mike


Brought to you by Super Global Mega Corp .com