This is a beginners Reversing Challenge. It is build with the optimization level set to 0 so that the assembler is more readable. If you are new to reversing, please remember that to solve Reversing challenges you probably need to know some C/C++, Assembler and also some experience with gdb (the gnu debugger). And maybe Ghidra. So this challenge is a great place to start Reversing, but unfortunately it's only 10 points because it's easier than other reversing challenges. It probably requires more skills than solving a 10 point Forensics problem like RubberDuck. If you solve the challenge you can use the flag to decrypt the sources and see how the challenge is created.
1 | Rivit |
2 | Gilad |
3 | vidar |
4 | Fish87666 |
5 | ebouteillon |
6 | Canlex |
7 | bobo1239 |
8 | kitty5kull |
9 | SunTzu |
10 | junwoo |
Can you send me a DM on discord?
Sure! Havent used it so far and maybe I can find others to do CTFs together. But I probably wont be able to make it this week.
Try binary ninja, it works pretty well: https://binary.ninja/
Okay, thanks man! Wanted to get started with Ghidra anyway. But doesnt seem Ghidra a bit overkill for a 10p challenge?
Nice, but because of the previous 2, I found it rather easy. agreed with @thebeltz that there is a small thing to think about
I have to admit...I dont get it. Even though people say its easy. I analysed it via objdump, stepped through it with gdb and got it to print the "whoop whoop" message (with my input of course). So any hints?
Can you send me a DM on discord?
Sure! Havent used it so far and maybe I can find others to do CTFs together. But I probably wont be able to make it this week.
Try binary ninja, it works pretty well: https://binary.ninja/
Okay, thanks man! Wanted to get started with Ghidra anyway. But doesnt seem Ghidra a bit overkill for a 10p challenge?
Nice, but because of the previous 2, I found it rather easy. agreed with @thebeltz that there is a small thing to think about
1 month ago
I have to admit...I dont get it. Even though people say its easy. I analysed it via objdump, stepped through it with gdb and got it to print the "whoop whoop" message (with my input of course). So any hints?