- Due Friday 10/5 11:59pm (1 day later for extension)
- Students must complete their own bombs, with discussion help.
- This assignment is self-grading. There is no explicit need to store your binary bomb in your Git repository, though it wouldn’t hurt.
- Collaboration policy: Academic honesty is expected, as always. For this assignment, academic honesty requires that you solve your bomb, and that you not disable the connection the bomb makes to our checking server. If you appear to have disabled this connection we will interpret your results as cheating. You may of course discuss your work with other students in the class.
A well-known Internet personality will deluge us with memes unless we defuse a
huge number of “binary bombs” he’s planted on our class server. A binary bomb
is a program that consists of a sequence of phases. Each phase expects you to
type a particular string on the 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!!!", deducting a half-point
from your problem set grade, 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 student a different bomb to defuse. Your mission, which you have no choice but to accept, is to defuse your bomb before the due date. Good luck!
Obtain your bomb by pointing your Web browser here:
Enter a username and your grading
server email address and hit
Submit. The server will return your bomb in a tar file called
k is the unique number of your bomb.
.tar file to a 64-bit Linux host, such as a CS61
VM. Move the file to the directory you want to do your work. Then run
tar -xvf bomb
.tar. This will create a directory called
k with the following files:
README.md: Identifies the bomb and its owners.
bomb: The executable binary bomb.
bomb.cc: Source file with the bomb’s main routine.
If you lose the bomb, no problem; just go back to http://cs61.seas.harvard.edu:15213/ and request it again.
Before running your bomb, read the entire assignment!
Your job is to defuse your bomb. This involves supplying it with just the
right input. But though there is a
bomb.cc file, it doesn’t actually contain
the code for the various phases. You’re going to be defusing the bomb using
assembly language, lucky you.
The bombs are tamper-proofed in a couple ways. For one, they can only be defused when the computer is connected to the Internet. Running the bomb on a machine without Internet connectivity won’t do anything.
You can use many tools to help you defuse your bomb. Probably the best way is to use your favorite debugger to step through the disassembled binary.
Each time your bomb explodes it sends packets to Internet personalities, who tell us, and you lose 1/2 point (up to a max of 20 points) in the final score for the problem set. So there are consequences to exploding the bomb. Be careful!
The first four phases are worth 10 points each. Phases 5 and 6 are a little more difficult, so they are worth 15 points each. The maximum score you can get is 70 points.
Although phases get progressively harder to defuse, the expertise you gain as you move from phase to phase should offset this difficulty. However, the last phase will challenge everyone, so please don’t wait until the last minute to start.
The bomb ignores blank input lines. If you run your bomb with a command line argument, for example,
then it will read the input lines from
psol.txt until it reaches the end,
and then switch over to stdin. Make sure to include a newline at the end of
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 registers and memory state. One of the nice side effects of doing the lab is that you will get very good at using a debugger!
The bomb notifies us automatically of your progress as you work on it. You can keep track of how you are doing, and compare (anonymously) with everyone else, by looking at the class scoreboard at: http://cs61.seas.harvard.edu:15213/scoreboard
This web page is kept updated to show the progress for each bomb. It may take up to a minute for new explosions and defusings to show up on the scoreboard. Also, the scoreboard displays time in UTC, so do not be alarmed if it appears that your bomb is reporting status for the future!
There are many ways of defusing your bomb. Hypothetically, you could even figure out the bomb without ever running the program, just from the machine code (and various tools like objdump). But it’s much easier to run the bomb under a debugger, watch what it does step by step, and reverse-engineer the input it wants.
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.
There are lots of ways to puzzle out instruction meanings: lecture,
the book, even the examples distributed as part of our lectures.
(For example, if you’re curious about the
leaq instruction, go to
the cs61-lectures repositories, and try “
grep leaq */*.s”.
Also try searching for the instruction name on Google: “
instruction”. But be
careful. There are two syntaxes used for x86-64 assembly language. We
use “AT&T syntax” in class and in the book, but many online
references use “Intel syntax,” which switches the order of arguments
and is different in other annoying ways. For instance, Intel calls
rax ( no percent). Read about the differences
in syntaxes in the Aside on p177 of CS:APP3e, or
The GNU debugger is a command line debugger tool available on virtually every platform. You can trace through a program line by line, examine memory and registers, look at both the source code and assembly code (we are not giving you the source code for most of your bomb), set breakpoints, set memory watch points, and write scripts. The CS:APP3e web site has a handy two-page gdb summary (TXT) that you can print out and use as a reference. Here are some other tips for using gdb:
- To keep the bomb from blowing up every time you type in a wrong input, you’ll want to learn how to set breakpoints.
- Some critical gdb commands for this pset are
x(for instance, try
x/20xw $rax—gdb names registers with initial dollar signs), and
scommand is sometimes useful and sometimes dangerous. Many of the related commands on these pages might also be useful. Check out, for example,
info reg, and
display. And do read the manual for these commands! It contains lots of helpful time-saving hints. To exit gdb use
- Many students really like the TUI interface obtained by running
gdb -tui bomb. Read up about the TUI
layoutcommand. Some people also like to run gdb under gdb-mode in emacs.
- Consider creating a file called
gdbautomatically executes all commands listed in this file every time it starts up. The command
set confirm offis useful here (if you get tired of questions like “Quit anyway? (y/n)”). For this lab, a breakpoint or two would be super useful too!! But:
BOMBDIR/.gdbinitmay not be loaded by default. (Check this by reading gdb’s startup messages. If you see an error about “
auto-loading has been declined,” then your
BOMBDIR/.gdbinitwas not loaded.) This is a security precaution. To get around it, create a file named
.gdbinitin your home directory containing “
add-auto-load-safe-path [BOMBDIR]”. (More on auto-load-safe-path)
- For online documentation, type “help” at the gdb command prompt, or type “man gdb” or “info gdb” at a Unix prompt.
This will print out the bomb’s symbol table. The symbol table includes the names of all functions and global variables in the bomb, the names of all the functions the bomb calls, and their addresses. You may learn something by looking at the function names!
objdump -d (or
Use this to disassemble all of the code in the bomb. You can also just look at individual functions.
This utility will display the printable strings in your bomb.
For more, don’t forget your friends the commands
the amazing Google and Wikipedia. In particular,
info gas has more
than you might ever want to know about assembler.
This lab was originally created for CMU’s CS:APP course.