This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
Gossip prune messages are subject to replay attacks #1952
Assignees
Comments
vkomenda
pushed a commit
to vkomenda/solana
that referenced
this issue
Aug 29, 2021
) Bumps [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) from 4.27.0 to 4.28.0. - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v4.28.0/packages/eslint-plugin) --- updated-dependencies: - dependency-name: "@typescript-eslint/eslint-plugin" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
CriesofCarrots
pushed a commit
to CriesofCarrots/solana
that referenced
this issue
Jul 2, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
Prune messages in Gossip are subject to reply attacks since they have no signature and origin/destination verification.
Proposed Solution
Prune messages should be signed and should only be processed if the node that received the message is the intended destination for it.
tag: @aeyakovenko
The text was updated successfully, but these errors were encountered: