netcode 1.4.2#168
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.
Version bump for 1.4.2. CMakeLists.txt and netcode.h move together for
release-check.yml.PATCH. No API change, no behaviour change, no wire change — the vendored crypto's observable output is byte-identical to 1.4.1, verified by differential test.
Ships the libsodium 1.0.21/1.0.22 hardenings (#167):
ACQUIRE_FENCEin all three AEAD decrypt paths — plaintext is not produced before authentication completes.crypto_verify_nconstant-time hardening — the function that compares the Poly1305 tag, now defended against the compiler optimising it into something branchy.Plus
test_crypto_aead_vectors, a known-answer test that netcode did not previously have despitesodium/NOTES.mdprescribing it as the primary validation.