[codex] fix noobzctf2023 mypin checker - #183
Open
alchemy1729-bot wants to merge 2 commits into
Open
Conversation
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.
Fixes #64.
What changed
.flag.sha256fornoobzctf2023/mypinflagCheckthat validates against the sibling.flag.sha256Why this change
The archived challenge was missing any checker path in ctf-archive. The jar itself is enough to recover the archived accepted input, and that recovered value matches the hash proposed in the issue.
Validation
I enumerated the jar's reachable input space from the archived challenge logic, identified the archived accepted input, verified that it matches the issue-reported hash, and then re-tested the branch version in a live pwn.college practice container for
noobzctf2023/mypin..flag.sha256andflagCheckinto/challengeflagCheck