strip(1): will it goof anything?

[Peter da Silva]

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