Skip to content
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

Reject expired data and log with debug level #4217

Merged
merged 4 commits into from
Apr 30, 2020

Conversation

ripcurlx
Copy link
Contributor

No description provided.

chimp1984 and others added 4 commits April 29, 2020 18:37
and do not broadcast.

It is unclear why we receive expired data (some are very old), but a
manipulated node might produce that and as it only removed at each
batch process running each minute to clean out expired data it still
could propagate. Is an attack vector also to flood the network with
outdated offers where the maker is likely not online.

Should fix bisq-network#4026
Should be set to warn level again with next release v1.3.5
Copy link
Member

@sqrrm sqrrm left a comment

Choose a reason for hiding this comment

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

utACK

@sqrrm sqrrm merged commit 88a93ca into bisq-network:master Apr 30, 2020
@ripcurlx ripcurlx modified the milestone: v1.3.5 Jun 4, 2020
@ripcurlx ripcurlx deleted the expired-debug-logging branch July 16, 2021 07:14
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.

3 participants