/explore
|
You are here 
|
knight.sc | ||
| | | | |
blog.timac.org
|
|
| | | | | CryptedHelloWorld: App with encrypted mach-o sections | |
| | | | |
reverse.put.as
|
|
| | | | | I smile when I think about this "feature"! I liked it so much that things got out of control and I wrote a crackme to show it. It happens because Apple doesn't follow their own documentation/specification and the reversing tools of the trade do. The result is that IDA terminates, disassemblers output the wrong disassembly, strings are messed up, LLDB disassembles the wrong code (not GDB), class-dump will fail, and the reverser looks at a weird Mach-O header. | |
| | | | |
www.m4b.io
|
|
| | | | | An online electronic journal repository for various projects, topics, tutorials, and other such texts, usually dealing with programming languages, reverse engineering, CS theory, object/binary analysis, formal methods, formal logic, and maybe, sometimes, even philosophy | |
| | | | |
atilaoncode.blog
|
|
| | | I read two C++ subreddit threads today on using the auto keyword. They're both questions: the first one asks why certain people seem to dislike using type inference, while the second asks about what commonly taught guidelines should be considered bad practice. A few replies there mention auto. This confuses me for more than one... | ||
