SSH tries to guess which pubkey to use, and occasionally gets it wrong. You can give it some hints by including the following in your ~/.ssh/config:
Host teamX.ctf.csail.mit.edu PubkeyAuthentication yes IdentityFile ~/.ssh/<name_of_priv_key_file> |
You can do anything you want to the team VM (you'll have root-level access); however, some things will break our graders and you won't get points. Here's a list of things you SHOULDN'T CHANGE:
Yes, the scrimmage has been cancelled, unfortunately, due to staffing constraints.
We're still working out the details for how to make this happen; we'll keep you posted. Once the teams are given access, they can do whatever they want to the VMs. Remote access will be provided via SSH, though we are also looking into alternatives.
Once turned on, the VMs are publicly accessible, and there's little that we can do (aside from asking nicely) to prevent other teams from trying to attack you. The challenges will be given out at the beginning of the competition, so you'll be getting a reasonably secure VM by default (SSH will be the only service enabled). However, this will require extra care in setting up firewall rules, etc, to prevent others from having inadvertent access to your VM before you're ready.
Certainly. Players are encouraged to install and upgrade whatever they want; however, any changes they make are at their own risk - we will not have tested our plugins to work with newer/different software versions.
Each plugin will come with a shell script that installs the plugin and sets up the backend service.
Yes, challenges will be released throughout the competition.
The PII will consist of strings of the form "piiXX_\[random string\]", where XX is the challenge number. |
PII is submitted on the "black market" (a page on the scoreboard). The algorithm for how this affects bank balance is being tweaked - the updated will be presented on Wed, 10/24 lecture.