Fix for 5.10 reshare denial of service via predicable instance ids #152
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
A reshare message can initiate multiple DKG instances. The request IDs for those DKG instances are
chosen deterministically by hashing the reshare message. Then, the DKG instances are performed by
the initiator in sequence. Given that instances become stale after one minute, it is possible to evict later
reshare instances from the buffer by reuse their instance ID or spamming the buffer. This will prevent the
legitimate initiator from finishing.
Solution: