Cracking

Hi all,

I disassembled the code in gdb. I found there no suspicious text that could mean the flag. The fact is there is plouf function where everything starts up. I found that the function accepts to parameters which are strings. When i step into in debug mode i read the stack and can say there are no strings which are being matched. Maybe there is something that calculates the string to be the flag. I tried also setting test al,al to "1" and got a yeah but was not the flag. I read also other topics. Some say "try radare". I will do this next. thx for reading...

Hi all,

I have found something interesting. This time i did not decompile the project, but looked in hex editor. There is something strange. I found strings which are outputs as results of passed arguments into the code and the idea was about the endings of strings which are also null. Therefore i watched out to print all the strings which are in the same order. I have seen there is a string in output but a little bit strange and i could not manage to serialize in order. I was dealing with feelings to pass over the code so simply it was to challenge, but no it has no acceptance. Next i will look after the constraints how the key is being managed in the assembly code.

thx for passion,

Hello all,

After researching i have discovered a tool. That made it easy.

Thx
 😉

 🙂 what tool?

Hi guys,
I solved this using GDB in combination with Ghidra. I got a hint by looking at an example of std::string::compare() in C++. Notice how it’s used then refer back to its location in assembly.

Hey Everyone, Hope you’re doing well.
I think i completed the challenge. i used cutter
Bravo, tu peux valider en utilisant ce mot de passe...
Congratz. You can validate with this password...
But the only text i get is this and theres no password for validation did anyone complete the challege please help.

I think you found the sentences the binary send when you have the good password... but you didn’t find this password, sorry.