OpenSSL - yank broken version 1.5.0 #139942
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
There's upstream work ongoing in JuliaWeb/OpenSSL.jl#46, yanking the latest release of a somewhat widely used package 5 months after release is going to be hugely disruptive. Yanking may be useful right after a version is released, but like this it'll only create pain to users. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OpenSSL v1.5.0 uses illegal operations in a finalizer, leading to errors or crashes from corrupting the task runtime state.
See
The OpenSSL issue has been open for over 3 months without engagement from maintainers.