Project

General

Profile

Actions

Bug #3870

closed

Technique "Sudo utility configuration": Technique is not correctly reporting when applied by multiple rules

Added by Olivier Mauras over 10 years ago. Updated over 10 years ago.

Status:
Released
Priority:
1
Assignee:
Matthieu CERDA
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Here is the correct result when one sudo directive is applied:

2013-08-22 18:17     result_success     default_sudo_settings     Default: sudo settings     sudoersFile     -     The sudoers file did not require any modification
2013-08-22 18:17     result_success     default_sudo_settings     Default: sudo settings     Install     -     sudo already installed
2013-08-22 18:16     result_success     default_sudo_settings     Default: sudo settings     Permissions     it_xx     The group it_xx is already present
2013-08-22 18:16     result_success     default_sudo_settings     Default: sudo settings     Permissions     it_xxx     The group it_xxx is already present

And here is the result when a second one is added in another rule:

2013-08-23 10:31     result_success     default_sudo_settings     Default: sudo settings     sudoersFile     -     The sudoers file did not require any modification
2013-08-23 10:31     result_success     oracle_sudo_settings     Default: Oracle basic     Install     -     sudo already installed
2013-08-23 10:31     result_success     default_sudo_settings     Default: sudo settings     Install     -     sudo already installed
2013-08-23 10:31     result_success     oracle_sudo_settings     Default: Oracle basic     Permissions     it_zz     The group it_zz is already present
2013-08-23 10:31     result_success     default_sudo_settings     Default: sudo settings     Permissions     it_xxx     The group it_xxx is already present
2013-08-23 10:31     result_success     default_sudo_settings     Default: sudo settings     Permissions     it_xx     The group it_xx is already present

Another example with another second rule:

2013-08-23 10:39     result_success     default_sudo_settings     Default: sudo settings     sudoersFile     -     The sudoers file did not require any modification
2013-08-23 10:39     result_success     perforce_sudo_settings     Tuning: Perforce     Install     -     sudo already installed
2013-08-23 10:39     result_success     default_sudo_settings     Default: sudo settings     Install     -     sudo already installed
2013-08-23 10:39     result_success     perforce_sudo_settings     Tuning: Perforce     Permissions     perforce     The user perforce is already present
2013-08-23 10:39     result_success     perforce_sudo_settings     Tuning: Perforce     Permissions     p4_admins     The group p4_admins is already present
2013-08-23 10:39     result_success     default_sudo_settings     Default: sudo settings     Permissions     it_xx     The group it_xx is already present
2013-08-23 10:39     result_success     perforce_sudo_settings     Tuning: Perforce     Permissions     perforce     The user perforce is already present
2013-08-23 10:39     result_success     perforce_sudo_settings     Tuning: Perforce     Permissions     perforce     The user perforce is already present
2013-08-23 10:39     result_success     perforce_sudo_settings     Tuning: Perforce     Permissions     perforce     The user perforce is already present
2013-08-23 10:39     result_success     default_sudo_settings     Default: sudo settings     Permissions     it_xxx     The group it_xxx is already present

I tried changing directive priorities, oracle_sudo_settings has now priority 10 but it hasn't changed anything.
The resulting issue, is that for rudder, the compliance isn't achieved and the reporting show an unknown state.

Actions

Also available in: Atom PDF