Remove check of /var/log/dmesg from OVAL #10145
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Don't check
/var/log/dmesg
using OVAL, because it may legitimately fail.However, the rule has a STIG ID, so I guess that modifying its check isn't so simple - whoever understands this, please clarify.
Rationale:
Unlike the output of the dmesg command, the corresponding file may be binary, and therefore unsuitable to be examined by the textfilecontent OVAL test, as that one assumes that the file is encoded in UTF-8.
Moreover, the removed checking regex was quite fragile, which was probably caused by the NX feature having different name on different platforms and the corresponding log entry not being designed as machine-readable.