A problem has been detected with the BoKS Manager 6.7 installation package for Red Hat 7. When the package was updated to include support for Red Hat 7.1, the setuid bit was lost from several files in the installation package (revision A4). This will cause issues when running programs that require the setuid bit to be set (see list below).
Resolution / Workaround
There are several ways to resolve this issue.
If you have downloaded the affected package (between May 6 2015 and October 28 2015) but not yet installed it, you should download the corrected version of the installation package, BoKSClient67-RedHat-EL7.0-x86_64.tar.gz, revision A5 that was published on Nov 4, 2015.
If you have already installed the package you need to manually restore the setuid bit on the following files ($BOKS_DIR defaults to /opt/boksm/):
This can be done either manually as root using the 'chmod' command in a BoKS shell (assuming default directory):
# /opt/boksm/sbin/boksadm -S
BoKS # chmod u+s $BOKS_DIR/bin/X11/xdl
BoKS # chmod u+s $BOKS_DIR/bin/pvi
BoKS # chmod u+s $BOKS_DIR/bin/rolelist
BoKS # chmod u+s $BOKS_DIR/bin/ssh-keysign
BoKS # chmod u+s $BOKS_DIR/bin/sshpkadm
BoKS # chmod u+s $BOKS_DIR/bin/suexec
BoKS # chmod u+s $BOKS_DIR/bin/swrole
BoKS # chmod u+s $BOKS_DIR/lib/boks_getsshkey
BoKS # chmod u+s $BOKS_DIR/lib/privrun
BoKS # chmod u+s $BOKS_DIR/lib/tcpcrypt
Or automatically by running the attached script fix_bm67_setuid.sh as root:
md5sum: c5c1089019b86b6d588209a81693a47f fix_bm67_setuid.sh
sha1sum: 31faec24bc9e3c1cd5419695f63cc21799cb6e75 fix_bm67_setuid.sh
For additional information, please contact firstname.lastname@example.org.
Still have questions? We can help. Submit a case to Technical Support.