[Bugfix] Derive external pub extension from the new and not old key schedule #108
Conversation
This file contains 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
stefunctional
previously approved these changes
Mar 8, 2024
|
I'm confused. It seems the test fails but only on wasm? |
Yeah, the cipher suite it used wasn't supported by wasm crypto provider. Fixed. |
Thank you for explaining! |
stefunctional
approved these changes
Mar 8, 2024
tomleavy
approved these changes
Mar 8, 2024
tomleavy
approved these changes
Mar 8, 2024
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.
The added test fails on main with
InvalidConfirmationTag. The reason is generating external join info using old epoch's key schedule.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT license.