Milan Lysonek
Milan Lysonek
@evgenyz Any updates? If you have done some investigation and reported downstream issue on IB side, it's enough. In such case, send me link to the issue, I will update...
Now, as the RHEL issue is there, no need to have github issue for tracking purposes. Closing this one to not have it on two places
@matusmarhefka Updated (pushed the change also to my fork PR so it's shown in that GH CI check as well).
As this issue has been reported to RHEL Jira, closing this one to not have it reported on two places.
Also caught by Automatus: - fail: sshd_use_approved_ciphers/correct_reduced_list.pass - fail: sshd_use_approved_ciphers/correct_scrambled.pass - fail: sshd_use_approved_ciphers/correct_value.pass - fail: sshd_use_approved_ciphers/correct_value_full.pass - fail: sshd_use_approved_ciphers/correct_variable.pass
As `sshd_use_approved_ciphers` got removed from profiles, I don't consider this issue relevant for now. The rule needs rework until that adding `blocked` label.
Okay, so I consider this issue as something we want to have fixed in 0.1.74 release and we should focus on now.
As we want DISA to change their approach and accept drop in files, adding `blocked` label
Yes, that would be best to have it in controls file
Weirdly, the rule is aligned in RHEL9 STIG.