You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During review of #9910 we have discovered that the policy_specific_content key might contain wrong values in its subkeys values.
For example, when we build RHEL 7 content and we open the internal resolved file build/rhel7/rules/install_smartcard_packages.yml, most of the items contain the correct RHEL 7 package name pam_pkcs11. But the policy_specific_content contains openssl-pkcs11 in checktext and fixtext, and which openssl-pkcs11 isn't the correct package name.
SCAP Security Guide Version:
current upstream master as of 2022-12-01 as of HEAD 0e9c453
There was an issue with the other keys as well (see #9894 ) that manifested only when built with Python 2. But that issue seems to be caused by different thing. Our issue doesn't depend on Python version.
The text was updated successfully, but these errors were encountered:
So the policy_specific_content does not use variables currently. That is by design, as it makes it easier to import the changes from the spreadsheet to the repo. However, it does seem to be causing some unintended consequences, as shown here. We do have the ability to create override files like rhel7.yml.
Therefore, mystery is solved - it's all literal strings. So I take the "infrastructure" label out, but is it a STIG issue? I feel that in these cases, we should have OS-specific STIG files s.a. the mentioned rhel7.yml, because the policy specific content is propagated to the compiled rule, and RHEL7 STIG content somehow contradicts the let's say RHEL8 rule.
Description of problem:
During review of #9910 we have discovered that the
policy_specific_content
key might contain wrong values in its subkeys values.For example, when we build RHEL 7 content and we open the internal resolved file
build/rhel7/rules/install_smartcard_packages.yml
, most of the items contain the correct RHEL 7 package namepam_pkcs11
. But thepolicy_specific_content
containsopenssl-pkcs11
inchecktext
andfixtext
, and whichopenssl-pkcs11
isn't the correct package name.SCAP Security Guide Version:
current upstream master as of 2022-12-01 as of HEAD 0e9c453
Operating System Version:
F 37
Steps to Reproduce:
Actual Results:
openssl-pkcs11 in policy_specific_content
Expected Results:
pam_pkcs11 in policy_specific_content
Additional Information/Debugging Steps:
There was an issue with the other keys as well (see #9894 ) that manifested only when built with Python 2. But that issue seems to be caused by different thing. Our issue doesn't depend on Python version.
The text was updated successfully, but these errors were encountered: