Repository navigation
fix: prevent replay of solved Altcha challenges - #41
Open
code-cap-com wants to merge 1 commit into
Open
code-cap-com wants to merge 1 commit into
code-cap-com wants to merge 1 commit into
Conversation
A solved challenge stays valid until it expires (5 min), and nothing marked it as used, so one solved payload could be replayed for every submission. After a successful verification (PoW and server-signature payloads) the challenge signature is stored in cache.app until the challenge's own expiry (fallback TTL 3600 s). A signature already present is rejected.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A solved challenge stays valid until it expires (5 min), and nothing marked it as used, so one solved payload could be replayed for every submission.
After a successful verification (PoW and server-signature payloads) the challenge signature is stored in cache.app until the challenge's own expiry (fallback TTL 3600 s). A signature already present is rejected.