You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sose fa079836b1 Update '' 1 year ago
image first commit 1 year ago
servers nvm 1 year ago
.gitignore modified .gitignore 1 year ago
log.txt first commit 1 year ago changed labels to key-value format 1 year ago Update '' 1 year ago changed labels to key-value format 1 year ago first commit 1 year ago
scoreboard.txt first commit 1 year ago
solutions.txt first commit 1 year ago first commit 1 year ago


It's back, baby

coming soon! check #slbr on irc for updates!

typo? you're out.

when you play, you'll be dropped in a fresh vm. on the way to your goal, any mistyped command will delete your vm and you'll be eliminated.

contact ~ben or sose on (in the #slbr channel) to sign up.

How it works

  • Each game has a series of challenges to complete, users are provided with a bash shell and a folder of clues.
  • The challenges are numbered 1-X.
  • Users must submit the solutions to each challenge to the admin, the first user to submit correct solutions to each challenge will win the game.
  • If at any point the user enters an invalid shell command, they will be eliminated from the game.


  • Configuring a new set of challenges is as simple as editing the solutions.txt file with their solutions, and providing new clues in the ./image/clues folder.
  • In the solutions.txt file, the line number of each solution corresponds to the challenge it is the solution for. Solutions may not take up multiple lines.


  • docker
  • pslist
  • jq
  • BSD style netcat (netcat-openbsd on debian)


  • Make sure your ports 1337, 1338 and 1339 are not exposed to the internet, as SLBR will use them internally
  • mkdir /home/slbr-admin
  • useradd slbr-admin -d /home/slbr-admin
  • usermod -a -G docker slbr-admin
  • chown slbr-admin:slbr-admin /home/slbr-admin
  • sudo su slbr-admin
  • cd
  • git clone
  • cd SLBRV2
  • You are now ready to manage an slbr game

Running the game

  • run ./ to start the listeners for various game events
  • run ./ <user name> </path/to/pubkey> to create a new user
  • All game events and user commands will be logged to log.txt
  • You can ./ to cleanup after a game has finished