Skip to content

Disable the Alert System inherited from ZEC/BTC#104

Open
hairetikos wants to merge 1 commit intoZclassicCommunity:masterfrom
hairetikos:patch-2
Open

Disable the Alert System inherited from ZEC/BTC#104
hairetikos wants to merge 1 commit intoZclassicCommunity:masterfrom
hairetikos:patch-2

Conversation

@hairetikos
Copy link

security issue: i actually removed this back in 2016 (see hairetikos/zclassic-103-master@df7549d and other commits), but it seems it got reinserted when ZCL re-forked the newer ZEC Sapling upgrade back then to fix the Sprout security issues.

this is the quickest way to disable the Alert System without having to touch the rest of the code:

(just return/return false immediately)

we can fully purge the unused code later on when also removing things like Onion V2 code (as we have Onion V3 now), and compiling with LTO can already remove dead code too.

note: the ProcessAlert return of false means the P2P handler in main.cpp will call Misbehaving for every alert message received. this is actually desirable... nodes trying to abuse the alert system will eventually get banned.

i actually removed this back in 2016 (see hairetikos/zclassic-103-master@df7549d and other commits), but it seems it got reinserted when ZCL re-forked the newer ZEC sapling upgrade back then to fix the Sprout security issues.

this is the quickest way to neuter it without having to touch the rest of the code, we fully purge the unused code later on when also removing things like Onion V2 code (as we have Onion V3 now)

note:  the `ProcessAlert` return of `false` means the P2P handler in `main.cpp` will call `Misbehaving` for every alert message received.  this is actually desireable... nodes trying to abuse the alert system will eventually get banned.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant