This is a school project: Here is part of the description:
Your job defuse your bomb. You must do the
assignment on a 64-bit machine.
You can use many tools to help you defuse your bomb. The best way is to
use your favorite debugger to step through the disassembled binary.
Each time your bomb explodes it notifies the bomblab server, and you lose
1 point (up to a max of 40 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 15 points each. Phases 5 and 6 are a
little more difficult, so they are worth 20 points each. So the
maximum score you can get is 100 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 even the best
students, 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,
unix64> ./bomb [url removed, login to view]
then it will read the input lines from "[url removed, login to view]" until it reaches
EOF (end of file), and then switch over to STDIN. In a moment of
weakness, Dr.~Evil added this feature so you don't have to keep
retyping the solutions to phases you have already defused.
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 the
memory states. 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.
If this seems like a project your interested in and are able to do. Please let me know asap.
5 威客就此工作平均出价 $14/小时
Hello, I have done a similar challenge for linux. I also have vast reverse engineering experience on Windows. What operating system is the executable running on? When is the due date ?