You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And then there are some indirect issues that just look a bit concerning, like #623.
I can see madler has made a few commits on the develop branch, last commit 13 days ago at the time of writing. There are also some suggestions for workarounds for some of the issues, but it's not easy to tell whether they are actually the right thing to do or if they just silence an error and could raise other problems.
As the CVE is rated high severity there is a sense of urgency to upgrade, but I would prefer to move to an official tag from madler rather than 1.2.12 with cherry picks from develop or workarounds from this issue tracker thrown over the top. For planning purposes, is there a 1.2.13 tag coming soon, or else what is the official recommendation for vstudio-based consumers?
I am looking to move to 1.2.12 as a result of CVE-2018-25032, but stymied by some issues in the Windows builds.
Things like:
And then there are some indirect issues that just look a bit concerning, like #623.
I can see madler has made a few commits on the develop branch, last commit 13 days ago at the time of writing. There are also some suggestions for workarounds for some of the issues, but it's not easy to tell whether they are actually the right thing to do or if they just silence an error and could raise other problems.
As the CVE is rated high severity there is a sense of urgency to upgrade, but I would prefer to move to an official tag from madler rather than 1.2.12 with cherry picks from develop or workarounds from this issue tracker thrown over the top. For planning purposes, is there a 1.2.13 tag coming soon, or else what is the official recommendation for vstudio-based consumers?
@madler
The text was updated successfully, but these errors were encountered: