Yes you're kinda correct, because that file is not a valid PE/ELF file, it is basically x86 & Aarch64 shellcode combined, as can be determine by the file size & the absence of a header. But you can totally load that shellcode using some tools, or copying that bytecode into a C file & calling it directly. You can also copy the aarch64 shellcode into a C file, compile it with a cross compiler & then run it with qemu, to get the aarch64 flag as well, that's also a viable solution In this video I wanted to depict yet another method of solving these type of challenges by emulating code

Thank you

Yes z3 is pretty amazing

Glad it was helpful!

Thanks. Yes you're right, second challenge can be solved using tools like stegsolver, I depicted just another method to solve that.

That topic is beyond my expertise, but once I learn this topic, I will definately make a video on this

@@RE_Adventures fair enough, appreciated ❤️

Thank you so much 💜

Thanks for the feedback. I will surely make a tutorial on Capstone

Indeed, reversing & pwning is hard to learn, because you have so much to learn at the starting, but once you learn the basics you will have a fun time learning & solving ctf challenges. For reversing, I would suggest you to learn assembly first. Also you can watch my baby-cpp video, in which I explained how to reverse a c++ binary. For pwning, just go to liveoverflow's channel & watch its binary exploitation series, I have learnt pwning from that. Other than that just have fun while learning rev & pwn, because it is a long, but fun, journey

Thank you!

In the most basic words using symbolic execution we can tell it(angr) to go explore each and every path of the binary provided until it errors out or completes execution(deadend). After the execution completes, the manager contains a list of all the states, from those states we are only interested in the ones which executed successfully, ie deadend, then we iterate through each & every state & check if the input given contains the flag's initial character, if so that is our input that we are looking for. Hope it helps