Spencer

I downgraded to 1.4.1 and I am able to switch container runtime succesfully  

This does appear to be a duplicate of #2675. I have found a work around to change the container runtime. But I find that on 1.5.1 I'm not able to...

While issue #2675 is closed, it only partially fixes the issue. Users still will get an error if kubernetes version is not defined. The user needs to enable kubernetes, select...

@ksatirli 🤚 Interested in testing

These 2 PRs combined would create a good workaround: https://github.com/mitre/saf/pull/1249 https://github.com/mitre/saf/pull/1250

Current work around Use `save generate threshold -c` and save to a file Use a python script to convert the threshold file from yaml to json use jq with jq...

Note: Even trying to use `@v4.33.1` instead of `@4` results in the same behavior

I suspect the fix will be to do something like what is done with the `cron.d` directory https://github.com/dev-sec/cis-dil-benchmark/blob/c845274efcf6e5f2e9307a780995a94c7bee0042/controls/1_3_filesystem_integrity_checking.rb#L50-L62

Here is another example `cis-dil-benchmark-1.3.2` https://github.com/dev-sec/cis-dil-benchmark/blob/c845274efcf6e5f2e9307a780995a94c7bee0042/controls/1_3_filesystem_integrity_checking.rb#L42-L64 Only 1 of the 3 following should match ``` describe.one do %w(/var/spool/cron/crontabs/root /var/spool/cron/root /etc/crontab).each do |f| ``` Yet all 3 files are failing ![Screen...

I believe this is the root cause https://github.com/inspec/inspec/issues/1279