Closed ax-mlee closed 1 month ago
D: oscap: == cURL info: HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
I see an underlying cURL error in the logs. Does the curl
itself work in your environment?
@evgenyz yes, curling manually does work and we verified that step. Apologies, should have included that.
Can I ask you to retest it again with updated container? cURL received some updates recently. And if that would fail again, can you please add to the report exact build version of cURL packages?
Also, why are you trying to evaluate F40 container against RHEL7 content?
@evgenyz, we are running openscap within an F40 container against other containers/OSes. The RHEL7 just happened to be the one we copied and pasted here as we were testing.
For reference, and if you'd like more context, we were following the guide in this article: https://candrews.integralblue.com/2023/09/scap-security-and-compliance-scanning-of-docker-images-in-github-actions-and-gitlab-ci/#:~:text=The%20GitHub%20Actions%20Code
I'll also run another test here soon and let you know.
For reference, and if you'd like more context, we were following the guide in this article: https://candrews.integralblue.com/2023/09/scap-security-and-compliance-scanning-of-docker-images-in-github-actions-and-gitlab-ci/#:~:text=The%20GitHub%20Actions%20Code
My word! Thanks for the link, very educational.
Thanks!
Description of Problem:
Hi,
When running something like
oscap info --verbose DEVEL --fetch-remote-resources --profiles ssg/scap-security-guide-0.1.69/ssg-rhel7-ds.xml
we are getting an error that says:OpenSCAP Version:
1.3.10
Operating System & Version:
Fedora 40 container
Steps to Reproduce:
oscap info --verbose DEVEL --fetch-remote-resources --profiles ssg/scap-security-guide-0.1.69/ssg-rhel7-ds.xml
Actual Results:
Error with HTTP/2 streaming it appears
Expected Results:
Profile downloaded successfully without errors.
Additional Information / Debugging Steps: