Upgrade OpenSSL to 3.5.3 #797
Merged
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
geofft
force-pushed
the
geofft/openssl-3.5.3
branch
from
b2f8f88 to
892a5a9
Compare
zanieb
approved these changes
Sep 18, 2025
Edward-Knight
approved these changes
Sep 18, 2025
Turns out this was a mistake that was only present in 3.5.3. The 1.x series was documented as: "The status nibble has one of the values 0 for development, 1 to e for betas 1 to 14, and f for release." But the 3.x series was always documented as: "OPENSSL_VERSION_NUMBER is a combination of the major, minor and patch version into a single integer 0xMNN00PP0L". 3.5.3 was the only version that used 0xF; they reverted that for 3.5.4 and this didn't get into any other releases. (See openssl/project#1621 and linked issues.) |
|
How 0xfun |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
No description provided.