CS 595G at UCSB
Welcome to 595g! This repo will help guide you through various important aspects of your server.
These servers are in place to facilitate a consistent environment for use in
solving challenges. As such, challenges will be distributed through the server
infrastructure. You can find currently live challenges in
During initial testing, you will likely want to attack the service running on
your local box in order to get the best view of the outcome (e.g. using gdb).
However, in your final solution scripts, you will need to modify your scripts
to attack the vuln server. The vuln server is located at
You will also submit your solutions via your server. To submit a solution, place
your solution script in the directory at
/opt/solutions/<challenge name>/ where
the name is the same as in the challenges directory. Don't worry your solution
being in any particular format -- I will read your code and figure it out
myself. (Obviously, follow good programming practices and make it readable ...)
Read SUBMITTING.md for more information on submitting solutions.
In order to provide the most real-world environment possible, you have root
access on your server. You can run commands as root using
sudo. No password is
required when doing this as the
ubuntu user. Be careful. Consider what you are
doing before executing commands as root.
The slides for the class are available on int80.net
There is a python virtual environment set up for you with some basic tools. You can access it with
The challenges (and this README) are publicly available: github.com/pcgrosen
You can use
scpto easily transfer files between your computer and server.
There are several restrictions in place on your servers to protect their integrity:
No inbound traffic is allowed on ports 5000-5999 ("challenge ports")
Inbound public traffic is only allowed on port 22 (ssh)
The vuln server is slightly different:
- Vuln servers can only be attacked from inside the cloud network (i.e. only from your server).
These servers are provided for your benefit. Do not abuse this privilege.
Do not attack infrastructure that is not part of a challenge.
Do not attack other students, except where explicitly allowed.
Follow all UCSB computer use policy.
Do not remove my key (labeled
manager) from your authorized keys.
Do not shut down your server (restarting is fine).
These servers are not for private use. Do not store sensitive data on them.
Do not perform non-class related activites on these servers.
Do not write to
~/595g-files. (I will overwrite it.)
If you accidentally violate one of these rules, please let me know as soon as possible, and I'll work with you to fix it.
If I find you in intentional or severe violation of these rules, I reserve the right to terminate or disconnect your server.