-
Notifications
You must be signed in to change notification settings - Fork 698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update ansible in sshd_use_approved_kex_ordered_stig #11148
Conversation
Update regex so it can fix the existing configuration instead of just adding another one Signed-off-by: Edgar Aguilar <edgar.aguilar@oracle.com>
Hi @Xeicker. Thanks for your PR. I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/packit build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change looks useful. But, please add a test scenario covering this situation.
I'm not sure how to implement a test for this. As OVAL won't check if there are multiple entries of |
Aha, then I think that the OVAL should be changed as well. I think the rule should fail if there are multiple (different) occurrences of the KexAlgorithm keyword in the config. I assume that multiple occurrences of the same item could make the configuration inconsistent and cause one setting overriding each other. |
This is to take into account conlflicting entries in kex configuration Signed-off-by: Edgar Aguilar <edgar.aguilar@oracle.com>
With the update in OVAL, the test wrong_value.fail will fail to be fixed with previous ansible content |
Code Climate has analyzed commit 151c9d8 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 57.0%. View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CI fail of Automatus on CS9 is expected because this rule isn't part of the RHEL 9 product. The CI fail of Automatus on SLE15 is caused by python-rpm not present anymore in the BCI that is used to build the container back end, therefore, it isn't caused by changes in this PR.
Description:
Rationale:
Review Hints:
Here what I got with existing code:
And with these changes: