KTRW: The Journey to Build a Debuggable iPhone
googleprojectzero.blogspot.com
KTRW: The Journey to Build a Debuggable iPhone
1–10 of 26 posts
Re: KTRW: The Journey to Build a Debuggable iPhone
#2More generally, what forums, irc channels, sites, etc. could I go to if I wanted to get into this community of researchers?
Re: KTRW: The Journey to Build a Debuggable iPhone
#3ETA: I ask because my other comment is about debuggable phone availability. IDA was always an extra gate for amateurs. I’m wondering how much access mere mortals have to the edgiest tools and information of this particular trade.
Re: KTRW: The Journey to Build a Debuggable iPhone
#4Where does one go about obtaining the phones they describe early in the post? What is the availability and cost for phones of this kind? More generally, what forums, irc channels, sites, etc. could I go to if I wanted to get into this community of researchers?
Re: KTRW: The Journey to Build a Debuggable iPhone
#5Where does one go about obtaining the phones they describe early in the post? What is the availability and cost for phones of this kind? More generally, what forums, irc channels, sites, etc. could I go to if I wanted to get into this community of researchers?
Pretty easy to find on twitter https://mobile.twitter.com/jin_store
Re: KTRW: The Journey to Build a Debuggable iPhone
#6Re: KTRW: The Journey to Build a Debuggable iPhone
#7Where does one go about obtaining the phones they describe early in the post? What is the availability and cost for phones of this kind? More generally, what forums, irc channels, sites, etc. could I go to if I wanted to get into this community of researchers?
From a more grey perspective, the dev-fused phones do get stolen and sold around.
Re: KTRW: The Journey to Build a Debuggable iPhone
#8I note that IDA Pro and LLDB are mentioned. How much penetration does NSA’s Ghidra have at this point, and is it expected to grow over time? I used IDA briefly in a past life and was really impressed with Ghidra, especially as an “open” offering. ETA: I ask because my other comment is about debuggable phone availability. IDA was always an extra gate for amateurs. I’m wondering how much access mere mortals have to the…
From a cost perspective, Ghidra has a decompiler (That works really well), and is free. I would imagine this will help with adoption. (Most other tools like Binary Ninja don't have a decompiler, as they are hard. Here is a project that takes the Ghidra decompiler and puts it into Radare https://github.com/radareorg/r2ghidra-dec ).
IDA is in a good position with all the existing documentation and tutorials, I think its just a question of how long it takes for Ghidra to get the same treatment.
Re: KTRW: The Journey to Build a Debuggable iPhone
#9I note that IDA Pro and LLDB are mentioned. How much penetration does NSA’s Ghidra have at this point, and is it expected to grow over time? I used IDA briefly in a past life and was really impressed with Ghidra, especially as an “open” offering. ETA: I ask because my other comment is about debuggable phone availability. IDA was always an extra gate for amateurs. I’m wondering how much access mere mortals have to the…
I don't know how many people are actually using it, but I've been to more then one con that has had a talk about using it. The talks focused on showing off features and/or trying to get people to use it. From a cost perspective, Ghidra has a decompiler (That works really well), and is free. I would imagine this will help with adoption. (Most other tools like Binary Ninja don't have a decompiler, as they are hard. Her…
The feature set is solid. I've been frustrated by a few minor things that are missing from Ghidra, but Ghidra also has several features that are missing from IDA, and other features are better designed than in IDA.
But the whole thing is crushingly slow, especially the parts written in Java. (The decompiler is written in C++ but is also slower than Hex-Rays.) That single difference would probably have been enough to make me give up and go back to IDA, if I didn't have an ideological commitment to open source. I can't stand slow programs.
The UI is poorly designed, even compared to IDA's... quirkiness. Lots of paper cuts.
On the other hand, unlike IDA, it doesn't randomly crash and lose your data! (It does sometimes throw random NullPointerExceptions, but those are caught and displayed in a dialog. Since it's Java you don't have to worry about memory corruption.)
Overall, I agree it's in a good position with respect to adoption, although it does have to compete with pirated IDA, as well as the other alternatives.
Re: KTRW: The Journey to Build a Debuggable iPhone
#10Can't imagine running that sort of thing in the cloud. And that's even before considering the security aspects.