[wip] authenticate swarm connections with a verification hook #96
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 patch is a protocol-level breaking change that authenticates clients by signing the noise handshake hash with the provided public key. Previously with the custom
peer-id
extension peers would send their id but there was no verification that a peer was who they reported to be.On top of this verified peer id, there is a hook available by passing in an
opts.verify()
function that receives the remote public key and a callback to reject or allow a connection from a remote peer. In cabal-client we can use this hook to do network-level blocks and also to implement the first part of invite-only cabals.