feat: add support for specifying noise #32
Merged
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
1 task
jacobheun
force-pushed
the
feat/noise
branch
from
7c63576 to
65d0bac
Compare
mpetrunic
reviewed
Mar 6, 2020
|
Per suggestions this now uses the exported |
|
I bumped noise to the 1.0 release, I think this should be ready to go. |
Co-Authored-By: Vasco Santos <[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.
This adds support for being able to specify transport cryptos
SECIOandNoisevia the respective boolean flags--secioand--noise. This is designed to match the configuration options for the go daemon PR.TODO
Add test runs for both secio and noise (depends on a stable version of(skipping this as we plan to deprecate secio anyway, might as well focus on noise testing going forward)libp2p-noise)Relates to libp2p/go-libp2p-daemon#158