Closed rrusinov closed 2 years ago
The Zlib team pulled their 1.2.12 release in favor of Zlib 1.2.12#2 to fix a security bug and prevent the further distribution of components which depend on the insecure version of Zlib. The Azure SDK does not directly consume Zlib but downstream components of the Azure SDK consume zlib, thus the Azure SDK is affected.
To resolve the issue, there are several possible solutions:
"overrides": [
{
"name": "zlib",
"version": "1.2.12#2"
}
]
Note that this will require that your version of vcpkg be updated to a recent version.
Hi @rrusinov. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve
” to remove the “issue-addressed” label and continue the conversation.
Hi @rrusinov, since you haven’t asked that we “/unresolve
” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve
” to reopen the issue.
Describe the bug Building azure-core from source fails. It tries to download zlib-1.2.12, but it doesn't exists on zlib.net.
Exception or Stack Trace Add the exception log and stack trace if available
To Reproduce Steps to reproduce the behavior:
resulting:
Code Snippet Add the code snippet that causes the issue.
Expected behavior Successfully build without any issues.
Screenshots If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):
Additional context Add any other context about the problem here.
Information Checklist Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report