Repository navigation
Document API 35 release verification and GOST half-close limitation - #86
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The signed API 35 candidate built from main b3a4788 loses final TCP bytes on immediate write half-close through official GOST 3.3.0. The production MASQUE dialer reproduces it without Android TUN; correcting only the server relay write/error order resolves the diagnostic case. No client workaround is added.
Add the dated acceptance report with all 79 procedure rows, explicit partial/deferred coverage and a targeted browser HTTP/3 follow-up. Update the English/Russian procedure to require consecutive payload/FIN without delays and direct-dialer isolation on failure; document the server limitation in both MASQUE guides.
Validation: exact-commit main CI passed 675 tests; signed installed APK readback matched. Executed 18 subscription and 21 final-priority subchecks passed; 54 authentication/hostname negative requests reached no origin token. Core forwarding passed 11 GOST variants plus SSH/SSH Jump. Browser follow-up confirmed 15/15 controlled h3 pages across direct/MASQUE/HTTPS preference, with DevTools, body tokens, independent origin and TUN/underlying capture. Normal public Chrome requests also confirmed Cloudflare and BrowserLeaks h3 without certificate exceptions or forced QUIC. TCP fallback rejected forced QUIC and passed ordinary h2 traffic. Temporary AVDs/fixtures removed; private raw evidence is not committed.
SOCKS5 UDP, Firefox/path-MTU permutations and deferred scenarios remain open. The reproduced GOST failure is unchanged; this is not full release approval.