Monorepo for infrastructure and challenges of SECedu CTF 2019.
Alternatives To Geegle3
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
a day ago499cc0-1.0Python
Mail-in-a-Box helps individuals take back control of their email by defining a one-click, easy-to-deploy SMTP+everything else server: a mail server in a box.
17 hours ago113otherPython
Insular email distribution - mail server as Docker images
Maddy3,842116 days ago40July 01, 202279gpl-3.0Go
✉️ Composable all-in-one mail server.
Papercut Smtp2,474
3 months ago28JavaScript
Papercut SMTP -- The Simple Desktop Email Server
Smtp4dev2,2411123 days ago69January 07, 202169bsd-3-clauseC#
smtp4dev - the fake smtp email server for development and testing
Padloc2,19215 days ago1November 14, 201970agpl-3.0JavaScript
A modern, open source password manager for individuals and teams.
Go Guerrilla2,14618a year ago2December 28, 201955mitGo
Mini SMTP server written in golang
4 months ago43agpl-3.0C
The magma server daemon, is an encrypted email system with support for SMTP, POP, IMAP, HTTP and MOLTEN,. Additional support for DMTP and DMAP is currently in active development.
27 years ago2February 04, 20161bsd-2-clausePython
Python SMTP Server for Humans
6 years ago7mitSwift
Send email to any SMTP server like a boss, in Swift and cross-platform
Alternatives To Geegle3
Select To Compare

Alternative Project Comparisons

UPDATES: We now have an updated infra open-sourced with more features and standard CTFd integration here: adamyi/CTFProxy


Monorepo for infrastructure and challenges of SECedu CTF 2019.


Everything is behind the settings of a fictional company, Geegle. Geegle has its own BeyondCorp-like zero-trust network via UberProxy. We have a working email server that supports company internal emails as well as inbound and outbound emails at geemail-backend, geemail-frontend, geemail-client, gsmtpd. All challenge descriptions are sent to team through emails. Challenge emails are unlocked as players progress in the CTF. Every challlenge has its own unified configuration file called challenge.libsonnet.See chals/pwn/geelang/challenge.libsonnet for an example. Its emails, container services, static files, flags, etc. are all in that single file. We have a shared server that every player connects to, as well as separate team servers for each of the team. The clustertype in configuration determines whether a specific service should run on the shared server or in a separate team server. This makes it possible that some services are shared to facilitate inter-team communication while some services offer isolation between teams.

Players send their flag to [email protected] to claim points. They can also interact with xssbot through company internal emails.

Binary challenges are also tunneled through UberProxy with websocket. See cli-relay, cli-static, and uberproxy/websocket.go. Static files are served using shared infra sffe, a general-purpose static file front-end on top of SSTable (leveldb).

Other infra services we have include: scoreboard, dns (internal DNS service used by all containers to help connect to uberproxy), gaia (internal authentication service), gae (a service like Google App Engine and Amazon Lambda), requestz (a simple network debugging service), mss (internal KV databse service integrated with Geegle services authentication).

Everything (Golang, Python, C, TypeScript, Bash, JSONNet, Java, PHP) are built with bazel. Containers images are pushed to GCR, while docker-compose files are auto-generated as well.



Running Your Own CTF

If you want to use the same Geegle infrastructure to host your own CTF, we are more than happy to support you. Simply remove all challenges from chals directory and put in your own challenges, and change the root BUILD file accordingly.

Please do let us know if you use Geegle infra to host your own CTF. We can't wait to hear about the amazing work you have done :)

SSL Certificates

Please put your HTTPS certificates and keys to infra/uberproxy/certs/ and change infra/uberproxy/ssl.go accordingly.

Building Container Images

Please build using Linux AMD64. Cuz it's hard to set up cross-compiling for C programs on mac, ceebs.

Build only:

bazel build //:all_containers

Build and tag locally (so that you can use docker-compose to boot them up):

bazel run //:all_containers

Commits submitted to master branch will be automatically pushed to, our container repo

If you are deploying your own CTF using this infra, please change BUILD file to push to a different container registry, since is not public.


Master Server (Shared Server)

bazel build //infra/jsonnet:cluster-master-docker-compose
docker-compose -f dist/bin/infra/jsonnet/cluster-master-docker-compose.json up -d

Team Server (Separate Isolated Server)

bazel build //infra/jsonnet:cluster-team-docker-compose
docker-compose -f dist/bin/infra/jsonnet/cluster-team-docker-compose.json up -d

Test Server (All-in-one Server)

bazel build //infra/jsonnet:all-docker-compose
docker-compose -f dist/bin/infra/jsonnet/all-docker-compose.json up -d


Copyright (c) 2019 Adam Yi, Adam Tanana, Lachlan Jones

To check the author for an individual challenge/infra service, check CODEOWNERS.

Open-sourced with love, under Apache 2.0 License.

Popular Server Projects
Popular Email Projects
Popular Networking Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
Capture The Flag