beast
beast copied to clipboard
Jeopardy-style CTF challenge deployment and management tool.
Validation and creation of db entry takes place in registration of the chall
Couple the requirements of the beast to run together with the server. Care also when starting any of the sidecars make sure that the challs which were deployed earlier have...
Fix all the TODOs we have. `git grep "TODO"` ``` core/auth/token.go:// TODO: change this from username to email. core/manager/challenge.go: // TODO: Later replace this with a manifest file, containing Information...
Currently, the initial clone that beast does for the remote repository takes time for large repositories with large depths. The initial clone for the remote repository can be done using...
Currently the only container runtime available for use is docker, while it is great it adds a lot of extra overhead. We can use more stripped down version of container...
Use multi stage docker image builds to dockerize beast. This might require mounting the host docker socket `/var/run/docker.sock` inside the container and then installing docker client inside. For configuration purposes...
Create a release strategy for beast. Make sure that no breaking changes enters into a stable release. Also annotate the challenges with the beast version they were deployed with.
Beast should have the ability to deploy multiple instances of the same challenge, to not overwhelm a single container with a lot of requests. These new containers should not disturb...
* Email * Discord/IRC.
Bumps [github.com/gin-gonic/gin](https://github.com/gin-gonic/gin) from 1.7.0 to 1.9.0. Release notes Sourced from github.com/gin-gonic/gin's releases. v1.9.0 Changelog BREAK CHANGES Stop useless panicking in context and render #2150 BUG FIXES fix(router): tree bug where...