[AUTO-CHERRYPICK] Patch openssl for CVE-2025-15467, CVE-2025-15468, CVE-2025-66199, CVE-2025-68160, CVE-2025-69418, CVE-2025-69420, CVE-2025-69421 - branch 3.0-dev#15627
Merged
jslobodzian merged 7 commits into3.0-devfrom Feb 3, 2026
Conversation
…-2025-68160, CVE-2025-69418, CVE-2025-69420, CVE-2025-69421 (#15592) Co-authored-by: = <=> Co-authored-by: jslobodzian <joslobo@microsoft.com> (cherry picked from commit bfb613e)
…s/package/pkggen_core_aarch64.txt
…s/package/pkggen_core_x86_64.txt
12 tasks
Restore ./Configure call that had been removed by bad cherry pick
Removed conditional check for test dependencies in openssl.spec. These perl dependencies are now needed for all builds, not just builds with tests.
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
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.
This is an auto-generated pull request to cherry-pick commit bfb613e to 3.0-dev. Original PR: #15592
In case of no merge conflicts, the PR is merged without approval because it's an automated cherry-pick of an already approved PR.
In case of merge conflicts, an AI-based conflict resolver will attempt to resolve conflicts and might make mistakes. The reviewer must check AI's work before approving.