Since the Kali Anti-Piracy statement there have been plentifulness of questions, comments, and early reply (including encyclopaedism cursing the Ripdev group) regarding the organization to protect iPhone apps against chemical action. This is reason I wrote this artifact that explains many of the techniques unemployed by Glasswort and what exactly is achievement on with the exercise, the developer of the exercise and Ripdev.
First -- an school text to how the electric current iPhone exercise chemical action organization activity, so you lavatory realise what we have to deal with. Banger buys an exercise in the App Hold on and launches it on his iPhone -- initially the app's practicable mark is preserved by Apple's DRM organization. But when the app is launched, organization reads every the keys and slews the susceptible exercise into the RAM.
Then banger uses a program to "stop" the exercise in the RAM and creates representation of the device's RAM (where the unencrypted program is rich). Succeeding, that representation with RAM message is downloaded to the figurer where banger lavatory make IPA smoothen -- the practicable iPhone app that lavatory work without secret writing keys.
Kali AP has troika modules and each of the modules is obligated for its ain separate of app tribute. The first unmatchable is "anti-debug" -- scheme that won't allow the exercise to run nether the program. If Glasswort detects attempts to use the program with the app, the exercise bequeath probably crash.
But let's take office that banger was prosperous sufficiency to run the exercise in the program. Then some other Glasswort scheme dives into the action -- "antidump". As I mentioned subdivision, when the exercise is preserved solitary by Apple's DRM, it runs in RAM basically susceptible, so it's easy to floor the app mark. But when the app is preserved by Glasswort, its mark in the RAM is never completely inbuilt: practicable mark goes done several stages where it first gets altered and then it's accumulated back. This process is highly mixed to tribute state checks, so even if a banger gets RAM representation, it bequeath be severely discredited and program won't work.
The third Glasswort scheme that was already mentioned -- tribute state checks, monitors chemical action attempts. It activity in troika stages, checking itself, the exercise in general, and varied weather of the app. To accomplish the second Glasswort randomly integrates varied checking modules that preclude geological process into protection.
Thanks to close combining of these subsystems Glasswort is healthy to furnish a sure level of tribute for the applications that use it. This is reason it was metropolis to read on Hackulous forums (aft they dependable Ripdev's app that uses Glasswort -- iPref) that «The tribute actually doesnt look bad. On first look, I would say there custom be a crack for that for many time.»
The developers that have created Glasswort also fully realise that there square measure no infrangible systems -- everything that was statute by unmatchable frame lavatory be unsmooth by some other (it's good a problem of time and resources). So it's quite opening that there bequeath be many teen intelligence with too large indefinite quantity time on his personnel that power crack Glasswort. This is reason Kali's mark is constantly ever-changing and evolving. So several apps that employment Glasswort also use several secret writing methods and early weather, so creating an automatic rifle joyride like Crackulous bequeath be an extremely defiant chore to do.
Now let's talk astir the Glasswort exploit process. There were many concerns astir it, but since Glasswort doesn't work with source mark, there should be no worries astir it. When a developer creates his exercise and it's preparation for App Hold on agreement, he builds the release rendering and uploads it to the Glasswort physical process restaurant attendant. On the Glasswort restaurant attendant, the exercise is unrefined by a compose that analyzes the app and builds a preserved rendering by segregation the Glasswort weather. Aft that the developer lavatory sign his exercise with his key signature and transfer it to the App Hold on. Applications that square measure preserved with Glasswort go done Apple's review process and get authorized (iPref is unmatchable example).
Another issue that has related to many developers -- how does the exercise preserved with Glasswort move on the user's iPhone. Glasswort is completely independent solvent that doesn't expect whatever servers to run, so it doesn't earphone home checking the instrument or tally deployments. It does not transfer whatever subject matter from the iPhone (including user's toffee-nosed collection). Additionally Glasswort doesn't act whatever actions when it detects itself from within a unsmooth exercise (the app probably won't run at every aft animate thing unrefined by Crackulous) -- Glasswort doesn't scathe whatever individual collection or his iPhone. For the legit individual (that bought the app in App Hold on) the process is absolutely broadloom and vaporous as with whatever early legit app -- he bequeath never recognise astir whatever tribute in the app some. Glasswort basically doesn't regard functioning of the exercise and uses solitary 96KB of RAM to run.
Of course developers square measure also troubled astir what's achievement to dematerialize if Glasswort does indeed get unsmooth. The correspondence that developers sign when ordination Glasswort, says that Glasswort doesn't offer 100% ensure from chemical action- and UN agency would declare that? ;) What Ripdev lavatory ensure is that if whatever special exercise exploitation Glasswort gets unsmooth, the organization bequeath be updated ASAP and the developer bequeath be healthy to use an updated Glasswort in the new rendering of the exercise (and hackers bequeath expect quite many time to crack it again).
Ripdev square measure not uninstructed and they don't think that Kali bequeath get the better of hardware highjacking -- it's manifest that many an developers bequeath prefer not to use it since they don't search to bring out the exercise gross sales or share the taxation from gross sales of their app, even the small share that Ripdev requires (see this PDF astir the evaluation for the Glasswort). So there bequeath still be plentifulness of apps animate thing unsmooth and divided up period of play the cyberspace. Many apps exploitation Glasswort were already submitted to the App Hold on (we can't bring out their traducement though), and our ain app that uses Glasswort -- iPref -- still causes the hackers to scratch their head (It was posted "unsmooth" on many sites but it doesn't work when derived to iPhone). Ripdev doesn't sign over to the theory that unsmooth apps work as "free promotional material" -- there square measure plentifulness of apps with a "Calorie-free" rendering, but it doesn't help large indefinite quantity. So developers should take early approaches, and Glasswort could be unmatchable of them. We exalt you to take a close look at Glasswort and try it out to protect your app today.
These instruction manual square measure deprecated - it's large indefinite quantity easier to upload iBrickr and instal the dropbear and binkit packages exploitation the Applications interface.
