Jan Černý

The remediations have been removed by https://github.com/ComplianceAsCode/content/pull/12946, only remediations that are left are for Image Mode and also for IB. That means removing remediations isn't possible and won't help.

The old-new test is disabled on RHEL 10 in contest in hardening/oscap/old-new/main.fmf by this `because: TODO - no old scap-security-guide release yet`

Using custom GitLab pipeline I have discovered that this issue isn't reproducible any more. I use current upstream master as as of 2025-07-16 as of HEAD 273862212586b718f5fb7940fc7df5f6a410f88c. In contest report,...

This ticket is the same misalignement as the one reported in https://github.com/ComplianceAsCode/content/issues/13033 After we started to investigate rule rootfiles_configured misaligned with DISA we quickly discovered that the rule rootfiles_configured maps...

This looks fine now: ``` jcerny@fedora:~/work/git/scap-security-guide (pr/12486)$ python3 tests/automatus.py rule --libvirt qemu:///system ssgts_rhel9 require_singleuser_auth Setting console output to log level INFO INFO - The base image option has not been...

IIUC most of the test functions don't return any return value, they rely on that the `set -e` will cause that once any command in the function returns non-zero value...

@teacup-on-rockingchair Excellent catch! I think it was originally designed as a filed that should contain just a single product but then it evolved. Unfortunately, at this moment it isn't well...

@dodys Can we close this now because we have the Ubuntu 24.04 product?

This problem has also manifested in daily productization today. current upstream master HEAD as of 2025-02-11 as of https://github.com/ComplianceAsCode/content/commit/8ec16c5e9a9decd56499263e4120e5fa2c494e81

The problem is that: The following requirements and recommendations apply to the element:~~Content containing the use of checking systems other than the OVAL and OCIL checking systems SHALL NOT be...