-
Notifications
You must be signed in to change notification settings - Fork 672
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
test scenario for service_bluetooth_disabled is not causing expected fail #11949
Labels
productization-issue
Issue found in upstream stabilization process.
Milestone
Comments
vojtapolasek
added
the
productization-issue
Issue found in upstream stabilization process.
label
May 6, 2024
Locally I cannot reproduce:
|
Needs more investigation from the testing env. |
All test scenarios for this rule pass on latest RHEL8. Moreover, 8.6 EUS ends in few weeks and no SSG updates there anymore. Thus, closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of problem:
There is a test scenario which should make the rule service_bluetooth_disabled fail. But the rule passes when it is executed.
SCAP Security Guide Version:
stabilization-v0.1.73, commit 0b096bc
Operating System Version:
RHEL 8.6
Steps to Reproduce:
Actual Results:
The scan after applying test scenario should return "fail", but it returns "pass".
Expected Results:
The test scenario returns "fail" and the remediation is performed. The final result should be "pass".
Additional Information/Debugging Steps:
The text was updated successfully, but these errors were encountered: