-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Upgrade libsodium to 1.0.18 #4359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I'm not adding test vectors for non-canonical pubkeys, as that would require grinding to find a private key corresponding to one of the 19 pubkeys that can be non-canonical.
according to changelogs backwards compatible and containing various optimizations: https://github.com/jedisct1/libsodium/releases https://fossies.org/diffs/libsodium/1.0.15_vs_1.0.16/ChangeLog-diff.html https://fossies.org/diffs/libsodium/1.0.16_vs_1.0.17/ChangeLog-diff.html https://fossies.org/diffs/libsodium/1.0.17_vs_1.0.18/ChangeLog-diff.html (EDIT by str4d): The update is not in fact backwards-compatible; the passing test cases added in the previous commit fail as of this commit.
|
Note to reviewers: the patches to pubkey validation and signature validation are applied separately, because the pubkey validation patch on its own fixes all except one of the test case failures, while the signature validation patch is necessary to resolve the last failure, and proves that the set of valid signatures was altered in libsodium 1.0.16. |
|
ACK. I also ran the tests on |
|
Addressed @daira's comments. |
daira
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: "validatio" typo in the last commit comment. Otherwise utACK.
|
Once I've updated the spec I'd like someone to check consistency with this PR, but that doesn't need to block merging it. (Needs one more review.) |
Some of the comments in the 1.0.15 code were incorrect.
2906fe3 to
0cca79a
Compare
|
Force-pushed to fix the commit comment. No change to PR. |
defuse
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK, looked over the old/new libsodium code to make sure the behavior is the same.
|
@zkbot r+ |
|
📌 Commit 0cca79a has been approved by |
|
⌛ Testing commit 0cca79a with merge 48550eab29a6415208881e52196cb53a33d03ed2... |
|
💔 Test failed - pr-merge |
|
Blocked on the new dependency being uploaded to the downloads server. |
|
@zkbot retry |
Includes patches that maintain consensus compatibility with libsodium 1.0.15 for Ed25519 pubkey and signature validation.
Replaces #4239. Closes #2872.