Hello,
I've noticed something interesting, which gave me several hours of headache.
When inst is performed on a system with nfsroot, setuid/setgid permissions are not, by default, placed. As such, if one is to update, say, /sbin/su, which requires setuid bit set, if such binary is located on a nfsroot filesystem, the setuid bit will not be placed when inst will upgrade /sbin/su.
I haven't found a way to overcome this bug with inst, the proper alternative is to list all the files with setuid/setgid permission set and compare the results after an upgrade/install; but this doesn't account for new files.
Is there a better way to solve this? Please note, this happens *only* on nfsroot systems; I haven't tried on systems with partial nfs root, so I don't know the extend of the bug.
Cheers!
I've noticed something interesting, which gave me several hours of headache.
When inst is performed on a system with nfsroot, setuid/setgid permissions are not, by default, placed. As such, if one is to update, say, /sbin/su, which requires setuid bit set, if such binary is located on a nfsroot filesystem, the setuid bit will not be placed when inst will upgrade /sbin/su.
I haven't found a way to overcome this bug with inst, the proper alternative is to list all the files with setuid/setgid permission set and compare the results after an upgrade/install; but this doesn't account for new files.
Is there a better way to solve this? Please note, this happens *only* on nfsroot systems; I haven't tried on systems with partial nfs root, so I don't know the extend of the bug.
Cheers!
_________________