-
Notifications
You must be signed in to change notification settings - Fork 741
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RHEL 7.4: Too many setuid bits removed #140
Comments
Hey @duk3luk3, you're right about the As for as for
So removing thew SGID from that binary is OK in my opinion. |
fixed by #199 |
Since OpenSSH 7.4/7.4p1 (2016-12-19)[0] (The default in Debian Stretch, CentOS 7 and others) the "UseLogin" option has been deprecated. Setting this option originally prevented usage of a "traditional" /usr/sbin/login-based login – but has been set to "no" by default since quite a while, so even if this role would be applied on a host with an older OpenSSH version, the default value should still be save. Fixes #140 0. https://www.openssh.com/txt/release-7.4
Since OpenSSH 7.4/7.4p1 (2016-12-19)[0] (The default in Debian Stretch, CentOS 7 and others) the "UseLogin" option has been deprecated. Setting this option originally prevented usage of a "traditional" /usr/sbin/login-based login – but has been set to "no" by default since quite a while, so even if this role would be applied on a host with an older OpenSSH version, the default value should still be save. Fixes dev-sec#140 0. https://www.openssh.com/txt/release-7.4
When running against RHEL 7.4 beta, these files have their setuid bits removed:
/usr/bin/su
/usr/sbin/netreport
/usr/libexec/openssh/ssh-keysign
This definitely breaks
su
. I don't know about the other files and if they should have setuid, but I suspect so.I'll open a PR to add these files to the whitelist for RHEL 7.
As a workaround, add the files to the
os_security_suid_sgid_whitelist
var.EDIT: I can't actually figure out how to apply the workaround - neither putting it into a group var nor in the playbook vars works... - I also don't know why it's acting as if
os_security_suid_sgid_remove_from_unknown
is set to true.I am running ansibe 2.3.1.0, installed the role by doing
git clone https://github.com/dev-sec/ansible-os-hardening.git dev-sec.os-hardening
in/etc/ansible/roles
, and this is my playbook:The text was updated successfully, but these errors were encountered: