Repository navigation
merge: upstream moonlight-qt b0af84ea (pairing/cert hardening, h264bitstream bounds, OpenSSL TLS deploy) - #21
Merged
Conversation
These aren't exploitable in moonlight due to clamping done on the read side.
It supports TLS 1.3 and PQ-KEX back to Windows 10, unlike Schannel
…stream bounds, OpenSSL TLS deploy) Brings in 8 upstream commits, 2026-10-07 to 2026-10-14. No conflicts; moonlight-common-c submodule (our mic fork) is unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
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.
Merges 8 upstream commits from
moonlight-stream/moonlight-qt(2026-10-07 to 2026-10-14, upstream headb0af84ea). The merge had no conflicts. Themoonlight-common-csubmodule (our mic fork) is unchanged, and.gitmodulesstill points at it.What comes in (8 files, +113/−8)
challengeResponseDatacheck, X509 parse failures are checked, and theQSslKeyalgorithm is no longer hardcoded (nvpairingmanager.cpp,identitymanager.cpp)bs_write_u(), restores the file headers that were removed by mistake, and dropswarn_offscripts/build-arch.bat)Checked
git diff --cached --stat origin/mastershows only those 8 files.Build - MoonlightVibe Windows x64andBuild - MoonlightVibe macOSboth succeeded on this branch (runs 38571546995 and 38571553442,workflow_dispatch). The release step was skipped in both.Not tested: nothing was launched, since the build host is headless. Pairing with a host is the thing to try by hand.
No version bump, so this lands without a release. Merge with a merge commit, not squash or rebase, so the next sync keeps its ancestry.
🤖 Generated with Claude Code