Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site codas.UUCP
Path: utzoo!decvax!harpo!whuxlm!akgua!akguc!codas!mikel
From: mikel@codas.UUCP (Mikel Manitius)
Newsgroups: net.unix
Subject: Re: strip(1): will it goof anything?
Message-ID: <305@codas.UUCP>
Date: Fri, 18-Oct-85 17:54:19 EDT
Article-I.D.: codas.305
Posted: Fri Oct 18 17:54:19 1985
Date-Received: Sat, 19-Oct-85 20:23:22 EDT
References: <127@ucdavis.UUCP> <2862@sun.uucp> <130@amc.UUCP> <2886@sun.uucp>
Distribution: na
Organization: AT&T Information Systems (SDSS) - Orlando
Lines: 14

> > 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.
> 
> 	Guy Harris

I just checked strip on System V release 2, it does not change the suid
bits, nor the ownership. It really does not do anything to the program
other than strip the symbol tables.
-- 
	Mikel Manitius  - ...{ihnp4|akguc|attmail|indra!koura}!codas!mikel