Explore >> Select a destination
|
You are here 
|
blog.timac.org | ||
| | | | |
theevilbit.github.io
|
|
| | | | | After my recent blog post, my old mate @_Dark_Knight_ reached out to me and he asked me a question: "Do you typically callout user apps that allow dyld_insert_libraries?" And a few similar ones, and I will be honest, I had no idea what is he talking about, if only I understood the question :D Despite the fact that my recent blog posts and talks are about macOS, I deal much more with Windows on a daily basis, probably like 95%, and macOS is still a whole new territory for me. So I decided to dig into the question and learn a bit more about this. | |
| | | | |
intrigus.org
|
|
| | | | | How to reverse engineer a Mach-O binary from BraekerCTF 2024 that breaks all tools. | |
| | | | |
blog.xpnsec.com
|
|
| | | | | In this blog we'll look at what it takes to construct an in-memory loader for Mach-O bundles within MacOS Ventura without using dyld. We'll walk though the lower-level details of what makes up a Mach-O file, how dyld processes load commands to map areas into memory, and how we can emulate this to avoid writing payloads to disk. | |
| | | | |
adnanthekhan.com
|
|
| | | In this post, I cover how I discovered a CI/CD misconfiguration in the Release Drafter GitHub action and demonstrated how it could have directly impacted a Google owned open-source repository (and many more!) that used it by tag instead of SHA. | ||
