-
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
fix for issue 11909 #12318
fix for issue 11909 #12318
Conversation
As debian 12 openssh version is 9.2, sshd_keep_alive_0 should be replaced with sshd_keep_alive.
Hi @a-skr. 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-sigs/prow repository. |
🤖 A k8s content image for this PR is available at: Click here to see how to deploy itIf you alread have Compliance Operator deployed: Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and: |
Code Climate has analyzed commit 60036d9 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 59.4% (0.0% change). 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.
LGTM
Description:
fix a bug in debian standard profile that was causing openscap exiting on an assertion.
Rationale
Fixes Assertion failure with Debian Bookworm #11909
As debian 12 openssh version is 9.2, sshd_keep_alive_0 should be replaced with sshd_keep_alive.
adding the rule satisfies the dependencies of sshd_set_timeout rule. The dependency was previously missing (as a consequence, the scanner exited with an assertion)