Repository navigation
chore(boringssl): update submodule and bindings - #25
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
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.
Summary
Update the BoringSSL submodule to
46e1bedbc69ece72df6434f0734027b24af345bf, regenerate the Nim bindings, and bump the package version to0.0.14.Add the CPace role enum and include upstream's new CPace and Keccak EVP sources in the existing build chunks so the new bindings compile and link.
Validation
The binding generation, Nimble installation, and nim-boringssl tests passed. Additional smoke checks passed for a CPace exchange and the SHA3-256 empty-input digest.
The nim-libp2p and lsquic builds have not been run.