We have RH based Linux images; on which I have to "apply" some "special archive" in order to upgrade them to the latest development version of our product.
The person creating the archive figured that within our base image, some permissions are wrong; so we were told to run
sudo chgrp -R nobody /whatever
We did that; and later on, when our application is running, obscure problems came up.
What I found later on: the call to chgrp will clear the setuid bit information on our binaries within /whatever.
And the actual problem is: some of our binaries must have that setuid bit set in order to function properly.
Long story short: is there a way to run that "chgrp" command without killing my setuid bits?
I just ran the following on my local Ubuntu; leading to the same result:
mkdir sticky cd sticky/ touch blub chmod 4755 blub ls -al blub
--> shows me file name with red background --> so, yep, setuid
chgrp -R myuser . ls -al blub
--> shows me file name without red background --> setuid is gone