-
Notifications
You must be signed in to change notification settings - Fork 219
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
Node should verify DHT message field "stored_at" #3412
Comments
sdbondi
added a commit
to sdbondi/tari
that referenced
this issue
Oct 11, 2021
- Keeps track of inflight SAF requests and only accepts responses for requests that are inflight - Checks that `stored_at` is in the past - Fixes tari-project#3412, 3410
sdbondi
added a commit
to sdbondi/tari
that referenced
this issue
Oct 11, 2021
- Keeps track of inflight SAF requests and only accepts responses for requests that are inflight - Checks that `stored_at` is in the past - Fixes tari-project#3412, 3410
sdbondi
added a commit
to sdbondi/tari
that referenced
this issue
Oct 11, 2021
- Keeps track of inflight SAF requests and only accepts responses for requests that are inflight - Checks that `stored_at` is in the past - Fixes tari-project#3412, 3410
aviator-app bot
pushed a commit
to SWvheerden/tari
that referenced
this issue
Oct 24, 2021
…project#3444) Description --- - Keeps track of inflight SAF requests and only accepts responses for requests that are inflight - Checks that `stored_at` is in the past - Fixes tari-project#3412, tari-project#3410 Motivation and Context --- See tari-project#3412, tari-project#3410 How Has This Been Tested? --- - New/existing unit/integration tests - memorynet - Manually
sdbondi
added a commit
to sdbondi/tari
that referenced
this issue
Feb 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A node should verify and add some checking to the "stored_at" field of a SAF message and not just blindly use this as the "LastSafMessageReceived" field as this can cause a node to poison its own "LastSafMessageReceived" so that it never receives any SAF messages again.
The text was updated successfully, but these errors were encountered: