Skip to content
Discussion options

You must be logged in to vote

To add. While the update to the golang.org/x/crypto package is always nice and welcomed, CRI-O is unaffected by this specific vulnerability. We are not calling or using this API, nor are any of our dependencies, as far as I can tell.

We should be good.

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by buckaroogeek
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants