investigate possible infinite recursion in requestQueryId #52
Labels
No labels
ActivityPub
advanced features
basic functionality
bug
DHT
evaluation
refactoring
security
test case
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: schmittlauch/Hash2Pub#52
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As long as
requestQueryId
receives aFORWARD
response, the closest entries from the cache are recursively queried until aFOUND
is received.FORWARD
possible solution: introduce a maximal recursion with a default return value
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.