by tW4r on 1/26/25, 11:22 AM with 36 comments
by lauriewired on 1/29/25, 2:36 AM
It gives a good overview of the development process as well as my motivations for creating it. The tool will also be on homebrew shortly :)
by adeon on 1/29/25, 1:50 AM
Am I right in looking at Malimite here and reading "Built on top of Ghidra decompilation to offer direct support for Swift, Objective-C, and Apple resources." that this is not a Ghidra extension but rather it is using a piece of Ghidra (the decompilation) like a backend? Malimite here is presented as its own piece of software.
Asking as a Ghidra noob who doesn't know all the ways Ghidra can be used: Would it make sense for something like this to be a Ghidra extension instead? I.e. give Ghidra some tooling/plugin to understand iOS apps or their languages better, instead of a new app that just uses parts of Ghidra. Also the Malimite screenshot in the page looks similar to Ghidra CodeBrowser tool.
Asking because it feels like it could be: from the little I've used Ghidra so far, looks like it is designed to be extendable, scriptable, usable by a team collaborating, etc. And Ghidra seems more holistic than just focusing on decompiling code.
by evanjrowley on 1/28/25, 10:40 PM
by saagarjha on 1/28/25, 8:23 PM
by commandersaki on 1/29/25, 1:20 AM
by stuckkeys on 1/30/25, 6:51 AM
by gondo on 1/29/25, 9:04 AM
by anxixddjs on 1/29/25, 1:08 AM