investigate possible infinite recursion in requestQueryId #52

Closed
opened 2020-06-24 01:47:41 +02:00 by schmittlauch · 1 comment
Owner

As long as requestQueryId receives a FORWARD response, the closest entries from the cache are recursively queried until a FOUND is received.

  1. investigate how it behaves on an empty cache
  2. investigate how it behaves with a rogue node never stating its responsibility with a FOUND, but instead not answering or returning a FORWARD

possible solution: introduce a maximal recursion with a default return value

As long as `requestQueryId` receives a `FORWARD` response, the closest entries from the cache are recursively queried until a `FOUND` is received. 1. investigate how it behaves on an empty cache 1. investigate how it behaves with a rogue node never stating its responsibility with a FOUND, but instead not answering or returning a `FORWARD` possible solution: introduce a maximal recursion with a default return value
schmittlauch added the
security
test case
labels 2020-06-24 01:47:41 +02:00
schmittlauch added this to the working EpiChord overlay (without k-choices) milestone 2020-07-02 01:03:09 +02:00
Author
Owner

I just got hit by this by running against a buggy version that never states its own responsibility but always sends a FORWARD.

Maybe not important for simulation scenarios, where no node is buggy or evil, but should be pretty easy to fix.

I just got hit by this by running against a buggy version that never states its own responsibility but always sends a FORWARD. Maybe not important for simulation scenarios, where no node is buggy or evil, but should be pretty easy to fix.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: schmittlauch/Hash2Pub#52
No description provided.