Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README.md: Add CSCTF24 #35

Merged
merged 1 commit into from
Feb 24, 2025
Merged

README.md: Add CSCTF24 #35

merged 1 commit into from
Feb 24, 2025

Conversation

rexdotsh
Copy link
Contributor

@rexdotsh rexdotsh commented Sep 8, 2024

Thank you for this amazing tool! This PR adds CSCTF'24, held on Aug 30, 2024.
Note: When using CTFd v3.7.3, I did run into a few issues, which might require some changes to the code.

  1. When running stage 5, to fix the 404 pages, it fails because it cannot find the text "Sorry about that". This is because it has been changed to "404 Not found" in a recent commit.
  2. The way the scoreboard is fetched seems to have been updated, because of the new scoreboard brackets feature introduced in v3.7.0, which broke fetching the list of teams on my end. I ended up adding it directly to the HTML for https://2024.csc.tf/scoreboard, but this might be worth looking into.

@zhuyifei1999
Copy link
Member

Oops my apologies I missed this PR.

I'll take a look at the issues you mentioned. Thanks for letting me know and sorry again for the late response.

@zhuyifei1999
Copy link
Member

When running stage 5, to fix the 404 pages, it fails because it cannot find the text "Sorry about that". This is because it has been changed to "404 Not found" in a recent commit.

Should be addressed by a71b873

The way the scoreboard is fetched seems to have been updated, because of the new scoreboard brackets feature introduced in v3.7.0, which broke fetching the list of teams on my end. I ended up adding it directly to the HTML for https://2024.csc.tf/scoreboard, but this might be worth looking into.

Hmm, I loaded a test CTFd with imported data from UIUCTF 2023, and all it loads that's sort of broken is /api/v1/brackets?type=teams with a trivial payload:

{"success": true, "data": []}

Stage 01 would save this to $PAGES_REPO/api/v1/brackets?type=teams.json and stage 02 would rename it to $PAGES_REPO/api/v1/brackets?type=teams. But if one were to rename it to $PAGES_REPO/api/v1/brackets. GitHub pages would load the file correctly.

Though this hack would probably only work for bracket-less CTFs. I could implement this, or I could properly archive scoreboard data for all branckets by hooking the CTFd.js code, which may end up about the complexity of the stage 08 hooking of challenge ... Wdyt?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants