How c4t-but-s4d/goldctf-2024 works
Main Components
• Checkers – For each service there is a corresponding checker (located under checkers/… directories). Group these and indicate that they “monitor” or “validate” the target services.
• Sploits – Similarly, there are sploit directories (under sploits/…) that contain exploitation or challenge-specific scripts.
• CI/CD & DevOps – Represent the GitHub Actions pipelines (under .github/workflows) which handle automation routines such as check-service tests.
• Infrastructure and Configuration – Although not a running component by itself, include any relevant infrastructure-related files like Dockerfiles, docker-compose files and configuration files for nginx, centrifugo, etc. They indicate deployment and runtime environments.
Relationships and Interactions
• The “cell-front” component can be shown connected to the “cell” service (and possibly other services if the front-end is used to administer or view data), capturing the separation between client-side (front-end) and server-side (backend) code.
• A CI/CD block (labeled “GitHub Actions / CI Pipeline”) that points to various components (services, checkers, possibly sploits) to suggest the automated integration, testing, and deployment flows that are built into the project.
Architectural Patterns and Design Principles
• Multi-language/Multi-service Architecture – Emphasis on a modular design in which each challenge is a separate “service”, developed with a language and technology best suited to the challenge.
• Health Checking and Monitoring – The separation of checkers, which are designed to verify the health, availability, and perhaps security of the services.
• Separation of Frontend and Backend – Notably in the “cell” service, where there’s both a service backend (services/cell/backend) and an independent “cell-front” internal front-end.
• Containers and Orchestration – The multiple Dockerfiles and docker-compose files indicate that services and checkers are containerized. Include a note on this and display connections to the deployment environment if applicable.
Technologies and Frameworks
• PHP, Python, C++ (for digger), Rust, and Go are the primary languages for the services.
• Svelte (and Vite) in “cell-front” indicates a modern JavaScript framework for the front-end component.
• Docker and docker-compose for container orchestration.
• GitHub Actions for CI/CD automation.