This can be a problem in case of a configuration file where only the last occurrence of a keyword is significant. Even in the case of configurations where only the first instance is significant, presence of repeating keywords is ambiguous.
Stages of the proposed fix:
make automated test checking this by each PR for RHEL-6, RHEL-7, Fedora content
make PRs fixing particular cases of failing services wrt to this issue
enhance the subcompliance kickstart to also include tests for these cases (to prevent regressions in the future)
The issue:
There's a large number of textfilecontent54 objects collecting only the first match:
This can be a problem in case of a configuration file where only the last occurrence of a keyword is significant. Even in the case of configurations where only the first instance is significant, presence of repeating keywords is ambiguous.
Stages of the proposed fix:
Relevant fixes / PRs:
/etc/grub.conf
fixes: https://github.com/OpenSCAP/scap-security-guide/pull/437/etc/login.defs
instance fixes: https://github.com/OpenSCAP/scap-security-guide/pull/438