Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 (Fortune 01.1b1); site graffiti.UUCP
Path: utzoo!decvax!ucbvax!ucdavis!lll-crg!seismo!ut-sally!ut-ngp!shell!graffiti!peter
From: peter@graffiti.UUCP (Peter da Silva)
Newsgroups: net.unix
Subject: Re: strip(1): will it goof anything?
Message-ID: <318@graffiti.UUCP>
Date: Wed, 16-Oct-85 22:09:52 EDT
Article-I.D.: graffiti.318
Posted: Wed Oct 16 22:09:52 1985
Date-Received: Sun, 20-Oct-85 17:32:34 EDT
References: <127@ucdavis.UUCP> <2862@sun.uucp> <130@amc.UUCP> <2886@sun.uucp>
Distribution: na
Organization: The Power Elite, Houston, TX
Lines: 11

> > One note.  An unmonitored strip, perhaps stuck inside a find, will
> > silently remove setuid bits throughout the find path...be careful.
> 
> Or run it as "root".  I can't speak for System V (thanks to COFF, "strip"
> consists of no less than 8 ".c" files, and I'm not about to see how it does
> the stripping), but it may not remove the setuid bits there.

I doubt strip does this on purpose, because any change to a file resets the
set-uid bits, as a security precaution. You may be right that running it as
root will leave things alone, though I doubt it. The documentation doesn't
say root is immune to this side-effect.