-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: ban peer unexpected response #5608
feat: ban peer unexpected response #5608
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack
I looked into the test failure. Just looks like a flaky test. Passes locally for me.
I do wonder if we should ban it so quickly though. If nodes are upgrading and a new message is being sent around old nodes could ignore it and run fine, but if they don't recognize it now they could ban perfectly good nodes. Maybe we need to have some kind of limiter, like repeated bad messages, or versioning of some kind?
a46df95
to
40b4d9f
Compare
…-addresses * development: chore: fix windows install (tari-project#5616) feat: ban peer unexpected response (tari-project#5608) fix!: add validator mr to mining hash (tari-project#5615) fix: check bytes remaining on monero blocks (tari-project#5610) fix: duplicate tari header in monero coinbase (tari-project#5604) fix: monero fork attack (tari-project#5603) feat: add mempool min fee (tari-project#5606) chore(tests): large block unit tests (tari-project#5599) fix: miner delay attack (tari-project#5582) fix: peer connection to stale nodes (tari-project#5579) ci(fix): artifact cleanup for diag-utils (tari-project#5613) ci(fix): update Windows installer for Minotari (tari-project#5614) chore: fixes monero build (tari-project#5612)
Description
ban a peer if they sent an unexpected message
Motivation and Context
audit finding, TARI-002