How red-cadets/vkactf-2024 works
Project Type and Purpose
• This is an open-source CTF write-ups repository (VKACTF-2024). Its purpose is to store, categorize, and present challenge files (“give”) and their corresponding solutions (“solution”) across multiple categories (crypto, pwn, misc, reverse, web).
File Structure Analysis
• Top-level: README.md and a single directory categories/.
• Under categories/: five subdirectories: crypto/, pwn/, misc/, reverse/, web/.
• Under each category: multiple challenge directories named like cry-1e-LFG, pwn-1e-Robbery-of-Uncle-Sam, etc.
• Inside each challenge directory:
• give/ – the provided files for the challenge.
• solution/ – the write-up folder containing:
– exploit/ (source code of the exploit),
– writeup.md (the narrative solution).
• Some code in give/ appears in various languages (Python, Go, protobufs), but there is no build/deploy pipeline or runtime server.
README Insights
• The README serves as an index to all write-ups, grouping them by category with hyperlinks to each writeup.md.
• Main Components:
A. Repository Root
B. README (index)
C. Categories (crypto, pwn, misc, reverse, web)
D. Challenge Modules (one per challenge)
E. Sub-components per challenge:
– “give” (input files)
– “solution” – includes:
• writeup.md
• exploit (code)
• img (supporting visuals)
• Relationships:
• The repository root contains README and the categories/ directory.
• Each category contains multiple challenges.
• Each challenge branches into two parallel streams: “give” (the problem statement/artifacts) and “solution” (the analysis and deliverables).
Architectural Patterns & Principles
• Hierarchical modularity: grouping by category, then by challenge, then by content type.
• Separation of concerns: original challenge (“give”) is strictly separated from analysis and artifacts (“solution”).
• Consistency: every challenge follows the same directory pattern, enabling automation (e.g., static site generator).
Technologies & Artifacts
• Markdown (writeup.md) for documentation.
• Python, Go, and protobuf files for challenge code.