Jan Černý

@teacup-on-rockingchair please check it, it's easy, the SUSE profiles are only changed so that the new rule doesn't get there

Closing because of no activity in last year.

I have rebased this PR on the top of the latest upstream master branch. I have extended the check to not match other immutable platforms and I have fixed the...

The reason is that our content requires 10 minutes but DISA's content requires 15 minutes timeout. I have found that we have lowered it to 10 minutes recently in https://github.com/ComplianceAsCode/content/pull/13347/commits/0a0fd0d59c1f808a018abcbdf92ce3f1d4edc15e....

I have investigated this issue. I have found that we have a bug related to CPE applicability of fixes. The remediation isn't performed because the fix is resolved as not...

I haven't investigated this one, but I think it can be another bug caused by https://github.com/ComplianceAsCode/content/issues/13552 because the `setsebool` command is located in `/usr/sbin` which is affected by this openscap...

This issue has been fixed or worked around by https://github.com/ComplianceAsCode/content/pull/13645. As of 2025-07-14, the issue doesn't appear in daily productization. Also, I can't reproduce it locally using autocontest. I used...

Here is my initial investigation: The rule `account_password_selinux_faillock_dir` passed during the image build because there wasn't any faillock directory set in configuration files. Since the rule passed the remediation for...

We have discovered that the reason why the remediation can't find the `semanage` command is that inside the remediation the `PATH` variable has value `/usr/local/bin:/usr/bin` which doesn't contain `/usr/sbin` which...

This issue is caused by a bug in OpenSCAP and has been reported in OpenSCAP in https://github.com/OpenSCAP/openscap/issues/2242.