Watson Yuuma Sato

This issue has been fixed on DISA's SCAP content `Red Hat Enterprise Linux 8 STIG Benchmark - Ver 1, Rel 8`. Ref: https://github.com/ComplianceAsCode/content/pull/10078/commits/df24f2352cca70afc107358c62bae3386b66d839

As of `disa-stig-rhel8-v1r8-xccdf-scap.xml`, this has not been fixed yet.

As part of the V1R9 STIG update, RHEL-08-020041 now uses `configure_bashrc_tmux`, but the typo in DISA's automated content persists. Ref: https://github.com/ComplianceAsCode/content/pull/10100

> security_patches_up_to_date Under SCAP 1.3 this rule should not have an OCIL check.

@jan-cerny I believe this should a blocker then

@jan-cerny I agree with you. I even think that alpha can be a bit bold on removing symbols, and beta more conservative and fixing problems with symbols.

Hi, could you tell us how have you tried to escape the `

@ermeratos You might want to separate the two checks into their own rules; or, if one of the checks can be considered an applicability condition for the other check, it...

/test 4.13-e2e-aws-ocp4-pci-dss-node

Could you clarify why it is not worth solving this? My understanding is that this object duplication can lead to miss-alignments between `package_installed`, `package_removed`, `service_enabled`, `service_disabled` rules, and increased data...