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

fix(dht): use limited ban period for invalid peer #4933

Merged

Conversation

sdbondi
Copy link
Member

@sdbondi sdbondi commented Nov 18, 2022

Description

  • changes ban period for a remote node sending an invalid peer from permanent to limited (6 hours).
  • adds more detail on the reason for the ban

Motivation and Context

Seeing permanent bans for this case. This should make diagnosis easier.

How Has This Been Tested?

Simple change

@stringhandler stringhandler merged commit 04a3a8f into tari-project:development Nov 18, 2022
@sdbondi sdbondi deleted the dht-limited-ban-invalid-peer branch November 18, 2022 09:00
sdbondi added a commit to sdbondi/tari that referenced this pull request Nov 23, 2022
* development:
  fix: add hidden types and seed words to key manager (tari-project#4925)
  feat: timestamp validation (tari-project#4887)
  fix: deleted_txo_mmr_position_to_height_index  already exists error (tari-project#4924)
  feat: add default grpc for localnet (tari-project#4937)
  first commit (tari-project#4926)
  v0.40.2
  fix(dht): use limited ban period for invalid peer (tari-project#4933)
  feat: upgrade tari_crypto sign api (tari-project#4932)
  v0.40.1
  chore: fix depreciated timestamp clippy (tari-project#4929)
  chore: fix naming of ffi functions and comments  (tari-project#4930)
  fix: set wallet start scan height to birthday and not 0 (see issue tari-project#4807) (tari-project#4911)
  v0.40.0
  chore: remove unused methods (tari-project#4922)
  fix: updates for SafePassword API change (tari-project#4927)
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.

2 participants