Confirm that the PHP 8.0 build fails without the patch for OpenSSL 3.2 #140
Conversation
This file contains 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
GrahamCampbell
changed the title
|
I'd rather not patch PHP 8.0, I don't see a reason to do so? |
|
This PR was created just temporarily to confirm that the other PR was good. OpenSSL 1.1.1 has known security vulnerabilities, and multiple other OS distributions that ship PHP 8.0 with OpenSSL 3.0 apply this patch - this is where it came from. |
|
Right, but PHP 8.0 is not maintained at all in a few days, so I don't think it will be a huge difference. |
|
I'd still like to make the change to have Bref 2 using the same OpenSSL version across the board. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.