-
Notifications
You must be signed in to change notification settings - Fork 1
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
DFBUGS-1159: Misuse of ServerConfig.PublicKeyCallback (CVE-2024-45337) #464
DFBUGS-1159: Misuse of ServerConfig.PublicKeyCallback (CVE-2024-45337) #464
Conversation
@black-dragon74: This pull request references [Jira Issue DFBUGS-1159](https://issues.redhat.com//browse/DFBUGS-1159), which is invalid:
Comment In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
/cherry-pick release-4.17 |
@black-dragon74: once the present PR merges, I will cherry-pick it on top of In response to this:
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. |
may cause authorization bypass in golang.org/x/crypto Update golang.org.crypto from 0.29.0 to 0.32.0 Signed-off-by: Niraj Yadav <niryadav@redhat.com>
fdfb01f
to
a8b742a
Compare
@black-dragon74: No Jira issue is referenced in the title of this pull request. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
/retitle DFBUGS-1159: Misuse of ServerConfig.PublicKeyCallback (CVE-2024-45337) |
@black-dragon74: This pull request references [Jira Issue DFBUGS-1159](https://issues.redhat.com//browse/DFBUGS-1159), which is invalid:
Comment In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
Hi @nixpanic, we do not have a bug for 4.18 for this CVE (wondering why...) |
/jira refresh |
@black-dragon74: This pull request references [Jira Issue DFBUGS-1159](https://issues.redhat.com//browse/DFBUGS-1159), which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: nehaberry. Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
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. |
a8b742a
to
d9e9d74
Compare
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: black-dragon74, Rakshith-R The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
6529155
into
red-hat-storage:release-4.18
@black-dragon74: [Jira Issue DFBUGS-1159](https://issues.redhat.com//browse/DFBUGS-1159): All pull requests linked via external trackers have merged: [Jira Issue DFBUGS-1159](https://issues.redhat.com//browse/DFBUGS-1159) has been moved to the MODIFIED state. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
@black-dragon74: #464 failed to apply on top of branch "release-4.17":
In response to this:
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. |
@black-dragon74: #464 failed to apply on top of branch "release-4.16":
In response to this:
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. |
@black-dragon74: #464 failed to apply on top of branch "release-4.15":
In response to this:
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. |
@black-dragon74: #464 failed to apply on top of branch "release-4.14":
In response to this:
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. |
may cause authorization bypass in golang.org/x/crypto
Update
golang.org.crypto
from0.29.0
to0.32.0