You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the addition of blacklists in #149 we can now null-route misbehaving peers that send invalid messages.
The primary decider for black-listing is the validator: it is application-specific and in position to detect invalid messages.
However, the validator interface currently only includes the message itself.
That means that the validator cannot see the peer that forwarded the message, only the original source of the message.
This severely limits the ability to detect misbehaving peers that replay old messages from other peers.
Proposed action:
extend the validator interface to include the peer that forwarded the message.
The text was updated successfully, but these errors were encountered:
With the addition of blacklists in #149 we can now null-route misbehaving peers that send invalid messages.
The primary decider for black-listing is the validator: it is application-specific and in position to detect invalid messages.
However, the validator interface currently only includes the message itself.
That means that the validator cannot see the peer that forwarded the message, only the original source of the message.
This severely limits the ability to detect misbehaving peers that replay old messages from other peers.
Proposed action:
The text was updated successfully, but these errors were encountered: