Category Archives: NCDC


Hello everyone!

After the NCDC this weekend, we decided it would be nice to have a place to congregate and have informal discussion about the event, and about future events.  We have started a channel on IRC at freenode.  Details below:

Channel:  #isucdc
Password: (currently no password)

Hop on and give your praises, express your concerns, and suggest improvements!

VM Disk Size

There has been many questions about the 20GB disk size regulation.  Here is how it is stated currently:

“When creating a virtual hard drive, you are required to use the “Thin Provision” option and to make the drive no larger than 20GB in size. Your total disk usage must remain under 160GB.”
We have decided to change it.  The important part is the 160GB limit as well as the thin provisioning. Here is the revised sentence:
“When creating a virtual hard drive, you are required to use the “Thin Provision” option. Your total diskusage for all VMs must remain under 160GB.”

NTP Server Now Available

Is the white team running an NTP server available to the blue teams to use? This would help us coordinate our logs, events and activities with white teams records of events.

Yes! An NTP server is now available at, or (the proxy server).

On Windows, right-click the clock, choose “Adjust date/time”, then click on the “Internet Time” tab.

On *nix systems, install ntpdate to easily synchronize with our server:


You can also install an NTP daemon to sync automatically upon startup. See the documentation associated with your distro for more information.

Shell Server Test Script now available!

The script to test your shell server is now available from inside the ISEAGE network at

You can grab and run this easily via command line (assuming you’ve set up your network interface properly):

chmod +x

Please note the difference between the java runtime (java) and java compiler (javac), as you will need both to function correctly!

The script automatically generates and deletes source files to run its tests. If you’d prefer to use these files for troubleshooting, simply set the PRESERVE variable near the beginning of the script to 1.

If you’d like to examine it on your local machine, it is also available here: compile_test.sh_.txt Remove the “_.txt” ending before running it.