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
net-libs/libsignal-protocol-c: Drop 2.3.3 #31334
Conversation
6efa18e
to
33356fa
Compare
Should I not use the |
Pull request CI reportReport generated at: 2023-06-06 22:09 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Pull request CI reportReport generated at: 2023-06-06 22:19 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Yes, if the bug is assigned to the Security Team you should use |
This ebuild is vulnerable to CVE-2022-48468 and is superceded by libsignal-protocol-c-2.3.3-r1.ebuild, which remains in tree. Bug: https://bugs.gentoo.org/905098 Signed-off-by: Randy Barlow <randy@electronsweatshop.com>
33356fa
to
c5ed38f
Compare
I've made this adjustment. Thanks! |
Pull Request assignmentSubmitter: @bowlofeggs net-libs/libsignal-protocol-c: Linked bugsBugs linked: 905098 In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
Pull request CI reportReport generated at: 2023-06-08 01:39 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
This ebuild is vulnerable to CVE-2022-48468 and is superceded by libsignal-protocol-c-2.3.3-r1.ebuild, which remains in tree.
Bug: https://bugs.gentoo.org/905098