Skip to content

Environment and tools built hacking pwn adventure

License

Notifications You must be signed in to change notification settings

bs1phc/pwn-adventure-fun

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Pwn Adventure Fun

Infrastructure and tools built for the 4-week Pwn Adventure 3 hacking sessions for ComSec

Tools Created

Accessing the Server

Connecting to the Server

The server is running with a hostname game.pwn3, so you'll need to add this to your /etc/hosts file with the IP of the server. For Windows, I think it's C:\Windows\System32\drivers\etc\hosts.

Default Team Creds

hash: db1e797da308f027c876c61786682f3b

Infrastructure Notes

There are three containers in the stack

  • postgres_database: The database container. Just uses alpine with postgres, no commands are run directly on this server, but holds volumes on /var/lib/postgresql/data for data and /var/run/postgresql for connection sockets
  • pwn3_master: This one basically handles game data, so accounts, mission progress and all that stuff. This is the container that interacts with the database running on postgres_database.
  • pwn3_game: The actual game logic. It's currently set to handle 10 instances, I have no idea if there is a suggested limit beyond apart from the obvious requirements of the host server. This is the container the players should connect to directly

About

Environment and tools built hacking pwn adventure

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 53.2%
  • Python 41.8%
  • Dockerfile 4.0%
  • Shell 1.0%