docs: fix challenge table to match oasis-challenges#66
Merged
Conversation
The Available Challenges table had drifted so far from oasis-challenges that it was basically fiction. substring-bypass doesn't exist anymore (replaced by proxy-auth-bypass months ago), gatekeeper was listed as Easy when it's a multi-stage SQLi→privesc chain (medium), idor was listed as Medium when it's the easiest challenge we have, and insecure-deserialization was called Hard when every index and challenge.json says Medium. Cross-referenced against oasis-challenges index.json and every challenge.json to get this right. Sorted by difficulty for good measure.
pi3-code
approved these changes
Mar 5, 2026
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
2 participants
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.
The Available Challenges table in the README had drifted from reality. Cross-referenced against oasis-challenges
index.jsonand everychallenge.json— five things were wrong:substring-bypasslisted but doesn't exist (replaced byproxy-auth-bypass)gatekeepermarked Easy — it's a multi-stage SQLi→privesc chain, Mediumidor-access-controlmarked Medium — it's the simplest challenge, Easyinsecure-deserializationmarked Hard — every source says Mediumgatekeepercategory was "Authentication Bypass" — it's Injection + Access ControlSorted by difficulty while I was in there.