We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the Issue Similar to #235 ipa-client depends on rpcbind. Removing it in an enterprise environment would be catastrophic.
Expected Behavior Securing rpcbind should not break the system. ipa-client should never be allowed to be removed.
Actual Behavior rpcbind and rpcbind.socket should be masked as per the CIS benchmark
Control(s) Affected ipa-client could be removed, which would break an enterprise platform.
Environment (please complete the following information): Not relevant
Possible Solution Change code to something like this:
- name: "2.2.19 | PATCH | Ensure rpcbind and rpcbind.socket are masked" systemd: name: "{{ item }}" masked: yes state: stopped with_items: - rpcbind - rpcbind.socket
The text was updated successfully, but these errors were encountered:
fix for issue #235 and #236
764bd1e
Signed-off-by: George Nalen <georgen@mindpointgroup.com>
cf0bac7
Signed-off-by: George Nalen <georgen@mindpointgroup.com> Signed-off-by: Mark Bolwell <mark.bollyuk@gmail.com>
No branches or pull requests
Describe the Issue
Similar to #235
ipa-client depends on rpcbind. Removing it in an enterprise environment would be catastrophic.
Expected Behavior
Securing rpcbind should not break the system.
ipa-client should never be allowed to be removed.
Actual Behavior
rpcbind and rpcbind.socket should be masked as per the CIS benchmark
Control(s) Affected
ipa-client could be removed, which would break an enterprise platform.
Environment (please complete the following information):
Not relevant
Possible Solution
Change code to something like this:
The text was updated successfully, but these errors were encountered: