Gabriel Becker
Gabriel Becker
I believe this one can be close. Can you confirm @matejak . It didn't close automatically because #8086 targeted a branch that was **not** `master` (which is the only way...
Fixed by https://github.com/ComplianceAsCode/content/pull/13830
> We might need the new rootfiles_configured on RHEL 9 as well. Isn't this new rule part of the RHEL9 already? https://github.com/ComplianceAsCode/content/blob/19d56a0eeb7e13564a0b7fcccc86c7d9af088aff/controls/stig_rhel9.yml#L997 Do you mean something else than that?
This problem is now manifesting on RHEL8 STIG as well.
Isn't the case that "oscap" command is generating an invalid ARF instead, because oscap-podman is just a wrapper. So we should rather look into oscap behavior when scanning a container....
Maybe the `gethostname` function is returning an empty string, which then is considered valid by the code (is not NULL): https://github.com/OpenSCAP/openscap/blob/97d8831fbf65528c3cde98f1c788ca8f7e252e63/src/XCCDF/result.c#L315
This is now manifesting in RHEL9 as well.
The waiver https://github.com/RHSecurityCompliance/contest/pull/498 is adding a waiver for `remember_present_password_auth` and not `remember_present_system_auth`, anyway this issue should apply for both cases, I'm updating the waivers to include this second test scenario...
This is the same problem described here: https://github.com/ComplianceAsCode/content/issues/13799#issuecomment-3223935686
/packit retest-failed