Path: utzoo!news-server.csri.toronto.edu!rutgers!uwm.edu!spool.mu.edu!sdd.hp.com!ucsd!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.internals
Subject: Re: rock-and-roll [Re: Retaining file permissions] [long]
Keywords: chmod, sed, awk... and good old *cat*!
Message-ID: <10710@dog.ee.lbl.gov>
Date: 7 Mar 91 02:26:36 GMT
References: <7391@mentor.cc.purdue.edu> <1991Mar6.234727.23298@athena.mit.edu>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Distribution: usa
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 18
X-Local-Date: Wed, 6 Mar 91 18:26:36 PST

>In article <7391@mentor.cc.purdue.edu> asg@sage.cc.purdue.edu
>(The Grand Master) writes:
>> The following is a letter I mailed that our friend at MIT would not
>> post for me (Our news poster was screwed up). ...

In article <1991Mar6.234727.23298@athena.mit.edu> jik@athena.mit.edu
(Jonathan I. Kamens) defends himself a bit.  I would like to add that I
probably would not have posted that particular article for Mr. Master
either (and how did you get a first name like `The' anyway? :-) ).

As it happens, this particular barn door was closed after a horse had
escaped.  There is no sense in arguing that `write not clearing set-id
could not possibly be a security problem', because it was.  One could
perhaps argue that `it is not now a security problem', but I would not
want to bet my systems on it.
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab EE div (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov