Donnerstag, 15. September 2016

Prometheus FAQ

Hello everyone,

many people have asked me lots of questions about my upcoming tool called prometheus.
This post intends to answer common questions:

Q: When prometheus will be released?
A: Planned releasedate is 31.12.16

Q: Will that work on Windows/Linux?
A: I plan to release a compiled commandline tool for OSX and linux. Windows is not planned at the moment. But i also plan to release all my sourcode so you could compile yourself.

Q: Will you make a GUI?
A: I might make a GUI for OSX. Not sure about anything else. It depends a lot on how much time i have.

Q: Does prometheus work with my device?
A: Yes, prometheus technically works with every iOS device. Because this is the first downgrade tool for 64bit i'm mostly focusing on that now. I haven't tested this with 32bit devices, but if there will be any issues i will look into that once i'm done with 64bit.

Q: Does that work with iOS XYZ?
A: So far i belive it works with all iOS versions up to iOS 10.0. I have only tested on iOS 9 and iOS 10, but there is no reason why it wouldn't work on iOS 8 for example. In case Apple changes something now, i will let you know about that, but at the moment all iOS versions should be compatible.

Q: Can i use this to upgrade to an iOS version which is not signed anymore?
A: Yes. Prometheus can not only be used for downgrading, but also for upgrading your device similar to odysseus. This means you can go from iOS 7 to iOS 9 even if only iOS 10 is signed at the moment.

Q: Do i need SHSH blobs / APTicket?
A: Yes. Prometheus heavily depends on APTickets and more important on the ApNonce inside the APTicket. This means that even if you have a valid APTicket, there is a chance this cannot be used (yet?) for downgrading.

Q: I savend my APTicket with savethemblobs/TinyUmbrella/ .... can i use those with prometheus?
A: It depends. Technically it doesn't matter what tool you use to save your APTicket, but what really matters in case of prometheus is the ApNonce. This is what decides if that APTicket can be used or not for downgrading with this method. I don't want to go into details right now, but once prometheus is released i'll explain in detail what conditions need to be met to downgrade, what is possible and what is not.

Q: My APTicket can't be used for prometheus. Does that mean i should delete it, throw my phone away, sell my house and leave my children?
A: NO! Don't ever delete you APTickets! Even if you can't use them with prometheus right now, you never know whether it'll be possible to use them in future with prometheus or a different downgrade tool. Prometheus goes an unusual way, which allows you to do very cool stuff on the one hand, but on the other hand it's usecase is very limited. There is a good chance that there will be different tools in future which can use your APTickets even if they can't be used right now.

Q: Do i need a jailbreak?
A: This is one of the things which excite me the most about prometheus. There are usecases where you can downgrade without the need of a jailbreak! I don't know all of these, but what i've seen so far hints that it's device specific whether you need a jailbreak or not. I've seen noncecollisions on iPhone5s and iPad Air. All devices which have noncecollisions are technically eligable for downgrading without jailbreak, but you need more! There are a few things you need to do to take advantage of these nonce collisions.
1. First you need to figure out what ApNonce is generated the most often. It doesn hurt if you write down the Top 5 nonces.
2. Second you need to request an APTicket for that nonce while apple still signs the iOS version you want to downgrade to.
You can do that with "tsschecker -d DEVICE -l -e ECID -s --apnonce NONCE"
For example: "tsschecker -d iPhone6,2 -l -e 6537582623 -s --apnonce 603be133ff0bdfa0f83f21e74191cf6770ea43bb"
3. Then when that version isn't signed anymore you will be able to downgrade.

Q: Will i still be able to use prometheus when i upgrade to iOS 10?
A: With every update introduced there is a chance that something changed which has influence on how nonces are generated. If your device does generate noncecollisions, you can do the following while the old version is still signed:
1. Update your device (only if you actually want this).
2. Use noncestatistics tool to figure out what nonce is generated the most often.
3. Request an APTicket for that nonce for the older version (iOS 9.3.5 for example) while it's still signed.
4. Done
If your device does not generate any collisions it doesn't matter what iOS version it's on as you'll need a jailbreak for downgrading.
(Unless apple updates stuff which makes prometheus not work on newer iOS, but we can't know about that until a jailbreak is released)

Q: What can i do right now to be able to donwgrade in future?
A: This is a very good question! At the time of writing iOS 10.0.1 is the latest version, but iOS 9.3.5 is still being signed.
What you should do no matter if you have collisions or not is to request APTickets for your device for iOS 9.3.5 (if you want to downgrade to 9.3.5 later) for the following ApNonces:
603be133ff0bdfa0f83f21e74191cf6770ea43bb
352dfad1713834f4f94c5ff3c3e5e99477347b95
42c88f5a7b75bc944c288a7215391dc9c73b6e9f
0dc448240696866b0cc1b2ac3eca4ce22af11cb3
9804d99e85bbafd4bb1135a1044773b4df9f1ba3
One of them should be enough, but it doesn't hurt to get APTickets for all of them. Better have saved a ticket too much than having you ticket you can work with.
If your device generates collisions, you should also save tickets for the nonce generated the most often.

Q: What are these nonces on your blog and why do i have to request APTicket for those?
A: I'll tell you more about that once prometheus is released, but right now it is enough to know that if you have APTickets for those nonces, you will be able to downgrade in futre by using a jailbreak.
(Unless apple does significant changes)

Q: My device generates collisions, do i still need to save APTickets for those nonces?
A: Yes, i would recommend so. It doesn't hurt and you'll be grateful in future when you decide to downgrade.



More questions?
Just send me a mail to tihmstar@gmail.com or ask on twitter @tihmstar :)

greets
tihmstar

Freitag, 9. September 2016

Noncestatistics

Hello everybody,
thank you very much for everyone who sent me nonces!

I wanted to research these collisions a bit and now i want to share what i found out so far.
Here are all collisions inside the files i got: https://ghostbin.com/paste/6k62b

It is also interesting that there are collisions between different devices of the same model, with different iOS versions.
You can see thoses stats here: https://ghostbin.com/paste/p74ng

This means that we can use an iPhone5s to generate nonces and find out which nonces are generated the most often with given iOS version. Then other people with iPhone5s can request APTickets with that nonce and hope that they will eventually get that nonce.
You don't need to send me any more nonces.
But you should still take your device, run it for a few hours and check what nonce is generated the most often. In case you're lucky and there is a nonce which repeats every now and then, you should definetly grab tsschecker and grab tickets for that specific apnonce (you can do that with --apnonce parameter), because that means you'll likely be able to downgrade without jailbreak!
Warning: i noticed that nonces change when updating to iOS 10, which means there are different nonces which repeat on my device.
In order to downgrade you need to have the device generate the same nonce you got the APTicket for.

In case your device does not generate collisions you should request some tickets with these nonces:
603be133ff0bdfa0f83f21e74191cf6770ea43bb
352dfad1713834f4f94c5ff3c3e5e99477347b95
42c88f5a7b75bc944c288a7215391dc9c73b6e9f
0dc448240696866b0cc1b2ac3eca4ce22af11cb3
9804d99e85bbafd4bb1135a1044773b4df9f1ba3
this will allow you (unless apple does significant changes to their bootloaders) to downgrade with a jailbreak.
Make sure to request tickets with these nonces even if your device does generate collisions. It doesn't hurt ;)

Stay tuned for more updates
greets tihmstar

Donnerstag, 8. September 2016

prometheus downgrade and nonce collision

Hello everybody,
as some of you might have heared already i've been working on something called prometheus.
Prometheus is much like odysseus a technique for downgrading.
With prometheus it is possible for the first time to downgrade 64bit devices!
A lot of people asked if this is 64bit only and if it's only for iPhone5s.
No it's not, but as this is the first tool to downgrade 64bit devices i'm focusing on that first.
32bit devices are supported by this technique and also are all 64bit devices.
The second question people asked is whether a jailbreak is required for downgrading.
The answer is: for some devices a jailbreak is neccessary, for some it's not.

The problem is i have no idea when a jailbreak is definetly required and when you can also downgrade without jailbreak.
Downgrade with jailbreak is always more likely to be possible than without, that means if you can't downgrade without a jailbreak, there is a chance you still can with a jailbreak.
My iPhone5s does not need a jailbreak, but all my other devices do need one.
I tried an iPhone5s from a friend and his iPhone can't be downgraded without a jailbreak.

I have no idea what is causing this, this is why i need your help!
So the basic idea of this tool is to run a replay attack of your saved APTicket much like in the good old days with iOS 4. Since iOS5 when APTicket were introduced there is a nonce stopping you from "simply replaying the APTicket".
So to be able to replay the APTicket we have to make the device to regenerate the same nonce.
There are two ways (i know of) to make the device regenearet the same nonce.
One requires a jailbreak and one if simply bad randomness.

So for reasons i don't know, my iPhone5s generates a few nonces over and over again so i can simply request a ticket for that nonce as long as it's signed and then keep rebooting it until i get the same nonce. Then i can just replay that APTicket and start the downgrade.
Of course there is more to downgrading than just replaying the APTicket with the nonce, for example there is still SEP and the Baseband. Just don't worry about that i got a plan for this.

Let's focus on the ApNonce for a now.
I need you help to figure out more about this bad randomness.
There is a tool i coded which is called "noncestatistics".
You can download it here: (OSX) https://github.com/tihmstar/noncestatistics/releases/tag/0.2
SHA1 (a1c0f78ad8b3c49bd10ea62006e551080cff5f81)
Sourcecode: https://github.com/tihmstar/noncestatistics

That tool will put your device in recovery mode, read out the ApNonce and write it to a file. Then it will reboot, read the nonce again and again write it to a file. This will continue until you stop it with Ctrl-C. Then it will reboot your device into normal mode and you can use it as if nothing happened. This is completely save. You can use -h for help.
 (in case something doesn't work you can set -a parameter to only set auto-boot to true)
If you want to help me, get this tool, connect your devices let it generate like 1000 or more nonces and email them to me (tihmstar@gmail.com). Make sure to write in the mail what device you're using and what iOS version is installed.
Maybe with this info we can figure out how we can use this for future downgrades.
Also you can do "noncestatistics -s FILE" to figure out what nonce is the one generated the most often (if there is any) and always request and APTicket for that nonce with tsschecker.

That's about it for this post,
stay tuned for more information

greets
tihmstar

Mittwoch, 13. April 2016

ApTicketDumper64

UPDATE:
After i wrote this blogpost and asked for people's opinion on twitter, i've been told, that the file i was trying to extract using an overcomplicated method also does exist on the filesystem at
/System/Library/Caches/apticket.der
Thanks to @eriksmets for pointing that out.
So knowing that file exists, makes releasing the tool completly pointless, as basically all it does is parsing some img4 payloads, extracting exactly this file and putting it into a nice plist. Well, now all of this is completely unnneccessary as you can simply backup this file (via ssh or ifile or sth) if you want to save apticket of your currently installed iOS.
Even though @xerub has pointed out that SEP will be bigger of a problem than i though at first, i still think 64bit downgrades will be possible one day.
At least something like odysseusOTA should work one day.
Meanwhile i need to wait for the latest iOS to be jailbroken, because i will have to restore when running my tests. Also i need to get a 64bit device to play with at first place.
I'll let you know, as soon as there is something interesting ;)

//original post

It's been a while since last time i blogged. I've been busy with studying and bunch of other stuff. I even stopped making videos for my YouTube channel. But hey, i'm still alive, still doing research on things, still coding and spending most of my free time on twitter.
Right now i've been working on some shsh / apticket stuff. I know many of you are interested in downgrade and so i've been making tools for bunch of stuff related to downgrades.
ota.tihmstar.net is a js script which fetches the plist which tells iOS devices to what firmware they can OTA upgrade. It's not exactly an "ota signing status website", because it doesn't give you any information whether some firmware is signed or not. But if ios devices are told they can update OTA to some firmware we can safely assume it's signed.
Those who want to experiment a bit and check real signing status of some device / firmware / ota / baseband combination, should checkout "tsschecker". That's a tool, which requests an apticket from apple and if it get's one, a restore is technically possible. With that tool it is possible to send requests specifying the device, ios, whether to use normal restore or ota update, whether to ask for baseband ticket or not, or even manually specifying a BuildManifest of a beta or sth.
Right now it's almost 3am an i should probably go to sleep, but instead i've been coding on a tool called "ApTicketDumper64". It's late and my ideas for namig tools or making GUIs become pretty bad, i know.
This tool is based on something i found lately. I don't want to go too much into detail right now, because i don't know yet whether i'm going to release the tool yet. That's kinda something i'd like to ask you. But first let me give you some information. I assume this is something which works only on 64bit devices for reasons only apple knows. As i don't have a 64bit testdevice i can only assume stuff and not really test everything i'd like to test. Basically what this tool allows you to do is to dump SHSH blobs / Apticket from a jailbroken device. I really belive that one day it will be possible to downgrade 64bit devices so saving blobs is always a good idea. But what if one missed the signing window and couldn't save blobs? For example i have iOS 9.1 installed on my iPhone 6 but right now the latest signed iOS is 9.3.1. I could use tools to save 9.3.1 blobs (savethemblobs or tinyumbrella etc.) but with ApTicketDumper64 I could save my 9.1 blobs right from device like it was possible with iFaith in the good old limera1n days.
I guess now is a good time for a *DISCLAIMER*: i *belive* that method is able to save blobs. What i'm getting does look like an apticket and imo should work. But i can't tell 100%, because i did not have a chance to test anything.
One could say that having something that's gonna most likely work is still better than having no blobs at all, but the thing is i don't know if apple cares about this. Releasing this tool *might* point them to something they *might* fix. I don't really care about not being able to dump blobs from device, but it might be possible to somehow use this for downgrading. I can't really test this right now, because i don't have a 64bit testdevice and also there is no jailbreak available for latest iOS. Messing around with blobs and stuff means i have to restore after most of my tests. The problem is, having to restore a 64bit device means i have to upgrade to latest ios, which means no jailbreak, which means no more test.
Lot's of people on twitter want to help me testing stuff. Imo there is no point for that, because i might get some information if tests done correctly, but still the person would have to restore, which i don't want.

So the question now is, do i release that tool offering a possibility to save blobs for people who forgot to save, but still have a jailbroken iOS?
On the one hand this would be a safe way of people helping me to get information like: does dumping blobs work for everyone or just a few, does it work across all ios versions etc.
On the other hand it would be a risk that apple might change things in future ios versions and i don't know how it will affect downgrades.
Apple might mess around and make stuff much complicated, but to be honest i don't think that current iOS devices can be blocken from certain downgrade methods once they are figured out.
Please tell me what you think about this, either in the comments section below or on twitter.

Samstag, 17. Januar 2015

What is NC2-app ?

Some of you may have noticed that i've been working on a secret project for a while. If you didn't, don't worry. I published only very very few information and told only a handful people about it.
This project is called NC2-app. That was kinda meant to be a codename for development, but at this point i'm no sure if i'll keep the name or change it later. So what is this NC2-app? NC2-app is basically a package manager or "store" how i like to call it. You can say it's a Cydia alternative.
So why is there a need for an alternative? I thinks most people see Cydia as a tool to install and remove packages. They open it up, install some stuff and close it. That's it. But Cydia is more, than just a package installer. It is responsible for a lot of background stuff, for example stashing applications, running daemons which do stuff and more. Usually jailbreaks just do their work at patching the kernel and disabling codesigning and some other stuff. From that point on Cydia does everything else. Of course Cydia depends on a lot of stuff like dpkg and bash and other packages, but when you open up Cydia and it runs, your system has everything setup so you can make use of the hacks.
Cydia is probably the only app, which runs on every single iOS release and idevice available!
(At the time of writing Cydia runs on iOS 2.0 - 8.1.2)
I think that's also the reason why it's kept quite simple. If you break it down at it's basics, it's a uiwrapper for libapt and a webbrowser.
The reason why i'm making an alternative is, because i see way more potential in such a store. There are many features i want to add and some things i simply want to change.  Cydia is open source, so in fact i could just take the code and directly work on it, but saurik is a special type of guy. I don't know him well, but from what i've heard and seen he likes to do things in his own ways. Which is not a bad thing, but it's quite hard (at least for me) to get into the code, understand it and change things the way i want them. I mean just cloning and compiling Cydia is quite challenging already. And i can see why many people who have ideas have problems to get into that or don't even have the time to figure that out.
If you take a look at Cydia's binary you'll see that it only contains an armv6 build. This is required, to keep the old phone supported.
I want to go a different way. Because there is so much i want to change i decided to write a package manager from scratch. Most of that is just ui anyway, because libapt does a pretty good job at maintaining the packages at system level. NC2-app will be compiled with the most recent Xcode version and contain an armv7, armv7s and an arm64 build so it's optimized for every device out there.
To get a better feeling and usage, i won't support anything under iOS 7.0 and iPhone 4. I think most people are on iPhone 4 or higher anyway so that's not really a downside. Also this allows me to use features, which Cydia can't use because of compatibility reasons. NC2-app (or short "NC2") is using things like Storyboard and autolayout and many other cool things.

What means NC and why is there a 2 ?
I started this project with a friend of mine and he came up with the codename. It basically means "NewCydia". This does not mean i'm planning to kick off Cydia from the scene (at least not now :P), in fact i'm planning to make it 100% compatible with existing repos and purchases. At some point in development repos will have the possibility to update and support the NC2 features, but at the same time they will be still compatible with good old Cydia.
The reason there is a 2 in the name is because that's my second attempt. NC-app (version 1), which is discontinued, has never been released, because i hit some barriers during development. For NC1 i didn't use libapt and tried to create everything myself. I wrote parsers and fetchers and grabbers and used dirty NSThread things to invoke shell commands, but at the end it ended up in a mess. It's a very organised mess, but still a mess. Everything was coded "wrong" and slow and when it came to actually installing the packages, i realized, that too many dirty workarounds would be needed to get that somehow working. Even though it was planned from the beginning to use libapt, i thought i could use a temporary way, which turned out as a big mistake. The reason i couldn't use libapt at that time is, that Cydia's libapt library is only compiled for armv6 and even though i got the headers, Xcode wouldn't link it, because armv6 build aren't supported (i think since Xcode 6) anymore.
In theory i could release a binary of that, since the source was 100% either coded by me or by people allowing me to use their code for whatever i need. But there isn't really that much to see. I also kinda don't want to release the code, because you'll probably would cut your eyes off after looking at the code xD
To be honest i never wanted to release the source for multiple reasons, but for NC2 i have no choice :/
Because i'm using libapt-pkg which is under GPLv2 i have to release the source, as soon as i start distributing the binary. In contrast to Cydia, which afaik was never distributed outside saurik's repo (i think mainly because it's not quite easy to compile), i'm afraid people might patch out things they don't like, but which are necessary (like ads). At the moment i have no idea how to prevent this, as i'm planning to keep the freedom jailbreaking gives us. I've heard about iMods, but i don't like the idea of insead of having freedom, changing apple's restrictions for iMods restrictions. I think my opinion on iMods could take up another whole blogpost, so i'll just skip this. For NC2 i'm planning to keep most of the environment as it is. Keep using mobilesubstrate from saurik's repo, keep using the default repos (including saurik's), keep Cydia/saurik doing the payment as long as i don't have my own. But even if i'll have my own payment server one day, which is not one of my priorities right now, i'm thinking of it as adding additional features instead of completely replacing and even if i get my payment server working good enough to be able to replace Cydia's, i'm planning to keep Cydia payments as alternative which you can always use.
So basically NC2 takes the ideas from the original NC-app and completely re-implements them. I also have a whole list of stuff i'm planning to add. NC2-app uses libapt for managing a lot of stuff and C++ and C for performance reasons.

Current progress
Right now i'm really really busy with school and other stuff. I really don't know why i started working on NC2 again. First i started to compile libapt-pkg and libapt-inst, because the versions Cydia uses are for armv6 so i can't link to them when i build for other archs. To compile these libraries took me several month, because i had no time, was lazy and had to fix a lot of stuff. Oh and i had no clue about C++ syntax, so i only fixed it in the end because of luck. I named the libraries libapt-pkg-nc and libapt-ins-nc so you can install both, mine and saurik's at the same time without conflicts, because i didn't make the effort to compile them for armv6 so they'd be compatible with Cydia. After having the libraries working it took me a while to find out, how to actually use them, because i had still no clue about C++ and there wasn't good documentation either, justs the code.
Right now i got working: get a package by knowing it's id and update lists.
At the moment i started working on the ui of the packagedetail viewcontroller (NCVCDetail) and today i implemented grabbing the price and purchase status for a package.
There is a lot of work and a lot of parser and fetcher need to be written, as well as some system stuff, but eventually with a lot of time i'll get it going :D

Community
Since i have to opensource NC2, i hope people will help me working on this. There is a lot stuff, which needs to be done, not only code. I need a designer, who make the icons and the whole ui, i need the community to think about what button to place where and many more. The app itself is just kinda halfway planned, there are things i didn't even think about yet, but which need to be implemented. So please tell me what features you want, how you want it to look like. Send me a tweet to @tihmstar or write me a mail: tihmstar+NC2@gmail.com
Tell me what features you want, give me some feedback or design some icons or views.
Bring in your ideas and help me to make a cool new store.
Please keep in mind, that at the time of writing this i have almost no time at all, so i'll put your suggestions on my todolist, but i won't provide you access to my repo right now or give you more information or sth.

If you have questions, feel free to ask (preferably on twitter)
It's 4am right now and i'm half asleep, so please excuse if there are grammar mistakes in the post or if i simply wrote some bullshit. I'm too lazy to recheck everything in detail

Montag, 30. Dezember 2013

iOS 7 untetherd Jailbreak for iPhone 4: "simple7break" 1.0

Hi everyone :D
After evasi0n7 was released with a huge drama i decided to update my JB tool to include the updated Cydia and the evasi0n7 untether, give it a name (simple7break) and make it userfriendly.

Ok let's get to it :D

What do you need:
- Mac (sorry this is Mac only, since it's a fun project without a real use/need)
- Java installed (that should be the case by default on Mac's)
- iPhone 4 model iPhone3,1 or iPhone3,2 (sorry that doesn't work with iPhone3,3 again it's a fun project)
- 5 min of time


So first you need to download simple7break
link: https://twitter.com/tihmstar/status/417612434505859072
make sure you only download it only from trusted sources, like links in my twitter acc ;)

There we go! Now you should have a file called "simple7break1.0.zip" which you need to extract.
Now you can chose either open a Terminal, cd into that directory and execute "./install"
or you simply doubleclick the install file in finder and chose "Open with terminal" if it asks you.
Now connect your iPhone 4 and put it in DFU mode. You know that mode, when you have to press Power + Home for 10 sec and then release Powerbutton, but keep still pressing Home for 15 sec.
You should now see that the ssh ramdisk tool starts doing stuff.
After it finishes doing it's magic, your device reboots and you should see the evasi0n7 boot screen, saying patching kernel and stuff. When your device boots up just unlock it and wait a bit.
After some seconds a popup shows up saying something like "no more space left on device", you can safely ignore this and tap ok if you want and be happy, because it works :D
Just continue waiting and eventually your device reboots again. Now you should see the evasi0n7 screen again (i really like that screen, that's why i show it to you twice :P).
After the device boots up the second time you should finally have Cydia on your SpringBoard yeay :)
Basically you're jailbroken now and good to go, but i really recommend reading further and doing this last step too. Open Cydia and let it configure the filesystem (you know, this thing which always happens when you open up Cydia for the first time). Then open Cydia again, go to the changes tab and hit update in the left to corner. That reloads the Packages and you should see at least 6 new updates (i think that were 6) including ncurses and evasi0n untether. Now it's very important that you DO INSTALL THE UPDATES. That will finally make everythink clean and solid.
This is needed because i modded the install script from the ncurses package to remove the preinst script (which caused errors for reasons i don't know) and with the update you do in cydia this get's fixed. In theory this is not that much important, but you know it's a "beauty fix" :P
Same for the evasi0n7 untether, which updates to give you the latest kernel patches by evad3rs.
(basically it reinstalls the same package with no modifications at the time of writing (version 0.2) but again, that's my "beauty fix" :P)
Well after you done the updates you're good to go :D
Have fun with this drama free iOS7 untethered Jailbreak.
If you have any questions or issues, feel free to contact me on twitter @tihmstar or on freenode irc in #openjailbreak channel (if you contact me on irc give me some time to respond and don't leave -_-)

Hope you enjoy,
tihmstar :D


Samstag, 9. November 2013

what is fuzzing

 <tihmstar> well basicall fuzzing is inputting maltious requests to a ?"process"? ?"parser"?
10:02 <tihmstar> the fuzzing we do is modifying a mov file
10:02 <tihmstar> then we try to open the mov file in mobileSafari hoping it will crash
10:02 <JBUni> because of the JIT compiler, right?
10:03 <tihmstar> by "fuzzing a file" we (at least i) mean modifying a file, basically randomly changing some bits
10:03 <tihmstar> *bytes
10:04 <JBUni> right, i get this
10:04 <tihmstar> we have a tool called zzuf which modifys the file for you, but since obvously there is a very low change to make MSafari crash by modifying some bytes we need to do it again and again
10:04 <tihmstar> therefore smart people around here (me included :P ) createt scripts/tools to automate this process
10:05 <tihmstar> all tools are a bit different
10:05 <JBUni>  i have a question about that, actually
10:05 <tihmstar> ok just ask
10:06 <JBUni> is it possible to insert syscalls in the form of hex, and have the kernel read those and redirect to a different part of memory, etc?
10:06 <JBUni> instead of just random bytes
10:06 <tihmstar> to the mov parser?
10:06 <JBUni> yeah
10:06 <tihmstar> well that's more of a exploit
10:07 <tihmstar> first you need to know if there is a bug and how to trigger it
10:07 <JBUni> ah, and to do that, we need to find out where the parser breaks, right?
10:07 <JBUni> okay
10:07 <JBUni> gotcha
10:07 <tihmstar> then you can start looking at the bug hoping you can let it do something more like just crasjing the process, like inserting malcious code
10:07  → sock__ (was sock__-) joined  ⇐ sock__ quit  
10:08 <JBUni> hmmm
10:08 <tihmstar> looking at fuzzycactus for example: you give it a mov file and it automatically does following things in a loop (until the device crashes): creates a fuzzed file with zzuf, opens that file in mobilesafari, waits some time, kills safari and the loop starts from beginning obviuosly the new fuzzed file is different than the one before
10:09 <JBUni> but with a program that runs randomly like this, you're unable to keep proper track of which bugs happened
10:09 <JBUni> isn't it better to manually fuzz files?
10:09 <tihmstar> no ...
10:10 <JBUni> hmm... ok..
10:10 <tihmstar> fuzzycactus also looks for crashes and copies them into a dir
10:10 <JBUni> so we are only interested in crash logs?
10:10 <tihmstar> no ...
10:10 — JBUni facepalms
10:10 <JBUni> ok, i'll be quite, please go on
10:11 <JBUni> quiet*\
10:11 <tihmstar> it also pairs the crash to the mov file caused the crash and to the parameters were sent to zzuf to be able to recreate the file (which you actually don't need since it also copies you the fuzzed file to the dir)
10:11 <tihmstar> if you have a really good crash we are interested in your fuzzed mov file AND your original file
10:12 <tihmstar> in this case send both files and the crashlog to crakun (i think his mail was but im not quite sure)
10:12 <JBUni> yeah, i know his email
10:12 <tihmstar> any questions?