If you want to use slip days you have to tell us before the deadline (by emailing Sudhanshu Gupta and Shuang Zhai). We won't by default assume slip days for late submissions.
No email submissions will be accepted.
The nefarious Dr. Evil has planted a slew of "binary bombs" on our machines. A binary bomb is a program that consists of a sequence of phases. Each phase expects you to type a particular string on standard input. If you type the correct string, then the phase is defused and the bomb proceeds to the next phase. Otherwise, the bomb explodes by printing "BOOM!!!" and then terminating. The bomb is defused when every phase has been defused.
There are too many bombs for us to deal with, so we are giving each group a bomb to defuse. Your mission, which you have no choice but to accept, is to defuse your bomb before the due date. Good luck, and welcome to the bomb squad!
11:59pm, Friday, February 14.
Step 1: Get Your Bomb
Each group of students will attempt to defuse their own personalized bomb. Each bomb is a Linux binary executable file that has been compiled from a C program. To obtain your group's bomb, one (and only one) of the group members should point your Web browser to the bomb request daemon at
Note that this will work only on CS department machines. It
won't work outside the department—even elsewhere on campus. If you are not on CS department machines, you could
ssh into any of the CSUG machine and use a text-based browser such as lynx—it probably is more fun that way ;-)
Fill out the HTML form with your email address and name,
and then submit the form by clicking the "Submit"
button. The request daemon will build your bomb and return it
immediately to your browser in a tar file called
bombk.tar, where k is the unique number of your
bomb. If you work in pairs, use only one student's information to request the bomb, and email the grad TAs who you are working with.
file to a (protected) directory in which you plan to do your
work. Then give the command:
tar -xvf bombk.tar.
This will create a directory called
with the following files:
README: Identifies the bomb and its owners.
bomb: The executable binary bomb.
bomb.c: Source file with the bomb's main routine.
If you make any kind of mistake requesting a bomb (such as neglecting to save it, or typing the wrong group members), simply request another (with the same information). If you change groups but have not had any explosions from your current bomb, again, request another bomb; we'll sort out the duplicate assignments when we do the grading. You can't request a new bomb just because you want to get away with the explosion penalty from your current bomb.
Step 2: Defuse Your Bomb
Once you have received your bomb from the bomb daemon, save it in a secure directory. Your job is to defuse the bomb.
The bombs are limited to run on the CS undergraduate network only. We have tried to enable all machines on the undergraduate network, but machines come and go. If your machine doesn't want to run the bomb executable, ssh to one of the cycle servers (cycle1, cycle2, cycle3.csug.rochester.edu) and run it there. Contact the TA with any problems related to this issue.
You can use many tools to help you with this; please look at the hints section for some tips and ideas. The best way is to use your favorite debugger to step through the disassembled binary.
Each time your bomb explodes it notifies the TA, and you lose 1/4 point (up to a max of 10 points) in the final score for the lab. So there are consequences to exploding the bomb. You must be careful!
The first four phases are worth 10 points each; phases five and six are worth 15 points each, for a total of 70 points. We will grade this lab on a scale of 0 to 70, and scale it back to 8 as each programming assignment contributes to 8% of the final grade.
The phases get progressively harder to defuse, but the expertise you gain as you move from phase to phase should offset this difficulty. However, the last phase will challenge even the best students, so please don't wait until the last minute to start.
The bomb ignores blank input lines. If you run the bomb with a
command line argument such as
To avoid accidentally detonating the bomb, you will need to learn how to single-step through the assembly code and how to set breakpoints. You will also need to learn how to inspect both the registers and memory. One of the nice side-effects of doing the lab is that you will get very good at using a debugger. This is a crucial skill that will pay big dividends the rest of your career.
Your group can consist of either 1 or 2 people.
Any clarifications and revisions to the assignment will be posted to the Blackboard forum.
Do be sure to work on the class machines. In fact, there is a rumor that Dr. Evil really is evil, and the bomb will always blow up if run elsewhere. There are several other tamper-proofing devices built into the bomb as well, or so they say.
There is no explicit turn-in for the main assignment. The bomb will notify us automatically after you have successfully defused it. You can keep track of how you (and the other groups) are doing by looking at the score board. This web page is updated continuously to show the progress of each group. (Again, note that it works only within the department.)
Hints (Please read this!)
There are many ways to go about defusing your bomb. You can examine it in great detail without ever running the program, and figure out exactly what it does. This is a useful technique, but it is not always easy to do. You can also run it under a debugger, watch what it does step by step, and use this information to defuse it. This is probably the fastest way of defusing it.
We do make one request, please do not use brute force! You could write a program that will try every possible key to find the right one. But this is no good for several reasons:
There are many tools that are designed to help you figure out both how programs work, and what is wrong when they don't work. Here is a list of some of the tools you may find useful in analyzing your bomb, and hints on how to use them.
Looking for a particular tool? Don't
forget, the commands