A deprecated open-source platform for hosting Capture The Flag (CTF) competitions, originally used for picoCTF 2019.
picoCTF is a deprecated open-source platform for hosting Capture The Flag (CTF) competitions, providing infrastructure for challenge deployment, user scoring, and competition management. It was originally used to run the picoCTF 2019 event and is designed to be adaptable for custom cybersecurity competitions. The platform includes web interfaces, APIs, and shell servers to deliver a complete CTF experience.
CTF organizers, cybersecurity educators, and institutions looking to host custom Capture The Flag competitions. It is intended for those who need a self-hosted, modular platform for running cybersecurity challenges.
Developers choose picoCTF for its instance-based challenge system that combats flag sharing, its modular architecture allowing customization, and its automated deployment tools using Ansible and Vagrant. However, it is now deprecated, with the maintainers recommending modern alternatives like CTFd or kCTF.
The platform used to run picoCTF 2019. (deprecated)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates unique problem instances per user to combat flag sharing, a core feature detailed in the architecture walkthrough that enhances competition integrity.
Separates web, API, and shell servers for flexibility, allowing customized deployments and independent scaling as described in the project overview.
Uses Ansible and Vagrant for configuration management, providing reproducible local and remote setups with detailed documentation in the quick start guide.
Includes tools for creating, packaging, and deploying CTF problems with templates, leveraging the picoCTF-shell-manager for efficient competition running.
Explicitly marked as deprecated with no updates or support, leading to potential security vulnerabilities and compatibility issues with modern systems.
Requires Vagrant and Ansible, with initial deployment taking 30-45 minutes and involving multiple virtual machines, making it cumbersome for quick testing.
Relies on older deployment methods like static VMs, lacking modern features such as containerization or cloud-native automation, as admitted in the deprecation warning.