Skip to content
This repository has been archived by the owner on Jun 27, 2023. It is now read-only.

feat: add strict signing validation for messages #84

Merged
merged 3 commits into from
Jul 8, 2019

Conversation

jacobheun
Copy link
Contributor

BREAKING CHANGE: If messages are not being signed, this change will result in them being dropped. A previous release of floodsub added signing by default, but any Floodsub version older than v0.16.0 will have their messages dropped. This is inline with the latest go pubsub behavior.

Depends on libp2p/js-libp2p-pubsub#20

Signed messages are now validated. If strictSigning is enabled (it is by default), messages must be signed.

Copy link
Member

@vasco-santos vasco-santos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good!

src/index.js Show resolved Hide resolved
@vasco-santos vasco-santos merged commit d1bb5aa into master Jul 8, 2019
@vasco-santos vasco-santos deleted the feat/validate-sign branch July 8, 2019 13:33
vasco-santos added a commit that referenced this pull request Jul 8, 2019
BREAKING CHANGE: If messages are not being signed, this change will result in them being dropped. A previous release of floodsub added signing by default, but any Floodsub version older than v0.16.0 will have their messages dropped. This is inline with the latest go pubsub behavior.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants