Small challenge for hackers/rust programmers
Go to file
Christoph J. Scherr f947dd559c
cargo devel CI / cargo CI (push) Has been cancelled Details
docs: add solutions to readme
2024-09-06 20:04:27 +02:00
.gitea/workflows initial commit 2024-09-05 15:49:56 +02:00
.github/workflows initial commit 2024-09-05 15:49:56 +02:00
scripts initial commit 2024-09-05 15:49:56 +02:00
solutions feat(c3): add time limit 2024-09-06 20:01:47 +02:00
src docs: readme and api docs for c3 2024-09-06 20:03:31 +02:00
.gitignore initial commit 2024-09-05 15:49:56 +02:00
Cargo.toml feat: c3 plus solution 2024-09-06 19:55:16 +02:00
LICENSE initial commit 2024-09-05 15:49:56 +02:00
README.md docs: add solutions to readme 2024-09-06 20:04:27 +02:00

README.md

Wooly-Vault

A few small challenges for ⚒️ Rust Hackers 🦀

Configuration

Each challenge requires some basic information to host:

  • secret - a string that if found signifies that the challenge was solved

  • addr - the network adress plus port the challenge should run on

  • verbosity - how verbose the logging should be

  • challenge - which challenge to host (there are a few)

The secret cannot be inputted with a command line argument, because the arguments can often be seen in the process view. You may either specify a secret in the 'WOOLY_SECRET' environment variable or input it interactively on start.

Challenges

There are a number of challenges:

  1. Connect by TCP

  2. Connect by TCP and send a special u16

  3. Connect by TCP, get sent dynamic math questions, solve them fast enough

Solution

Solutions for some challenges can be found in [./solutions/]. Don't spoil the challenge for yourself.