From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,9960fa51a4a478af
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-02-10 13:55:10 PST
Path: archiver1.google.com!postnews1.google.com!not-for-mail
From: dewar@gnat.com (Robert Dewar)
Newsgroups: comp.lang.ada
Subject: Re: ACT announces availability of GNAT 3.14p
Date: 10 Feb 2002 13:55:09 -0800
Organization: http://groups.google.com/
Message-ID: <5ee5b646.0202101355.2c8d7ebb@posting.google.com>
References: <5ee5b646.0201301849.4e951bcb@posting.google.com>
 <e7ebd224.0202061336.767f7a9d@posting.google.com>
 <ud6zhqqkv.fsf@gsfc.nasa.gov>
 <5ee5b646.0202071709.11b3f88c@posting.google.com>
 <87ofixit6v.fsf@deneb.enyo.de>
 <5ee5b646.0202101038.68b3b71f@posting.google.com>
 <87n0yhf8e1.fsf@deneb.enyo.de>
NNTP-Posting-Host: 205.232.38.244
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1013378110 14558 127.0.0.1 (10 Feb 2002 21:55:10
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 10 Feb 2002 21:55:10 GMT
Xref: archiver1.google.com comp.lang.ada:19843
Date: 2002-02-10T21:55:10+00:00
List-Id: <comp.lang.ada>

Florian Weimer <fw@deneb.enyo.de> wrote in message news:<87n0yhf8e1.fsf@deneb.enyo.de>...

> /tmp is shared on multi-user UNIX systems, and if a 
> malicious local ...

Yes, sure, but in practice, this function is not used in
user programs (unless they specifically want to use /TMP
in which case they acquire this well known liability), but
only during certain development steps. If you are doing
Ada development on a machine where malicious users can
create links suddenly, you have a whole host of problems
NOT related to /TMP at all.

That's the point here. I agree that if all, or even some,
generated Ada programs used /TMP silently, there would be
a problem, but this is not the case, and has never been
the case.

Requiring the compiler and build tools to avoid the use
of /TMP seems an unreasonable suggestion to me.