Add early data support to Noise protocol #853
Draft
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
Signed-off-by: varun-r-mallya <[email protected]>
|
@varun-r-mallya : Ccing @acul71 , who needs Noise protocol in the upcoming interop efforts. Also, CCing @pacrob. |
…ent serialization test Signed-off-by: varun-r-mallya <[email protected]>
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.
What was wrong?
Discussion #837
How was it fixed?
I have started by adding a new noise early data handler module similar to the go implementation. Got rid of noise pipes and all the things removed from spec. WIP.
Isn't completely fixed yet. All tests pass, but the tests are not extensive enough.
To-Do