Difference between revisions of "Address bruteforcing"
(Added a draft of a matrix for better overview about the progress of the project...) |
|||
| Line 20: | Line 20: | ||
|- | |- | ||
| iPod nano 4g | | iPod nano 4g | ||
| − | | | + | | crashed |
| No | | No | ||
|- | |- | ||
| Line 31: | Line 31: | ||
| No | | No | ||
|} | |} | ||
| + | |||
| + | The staus "crashed" means that the device has crashed when putting in the modified notes but we couldn't find a address (yet) that is exploitable. | ||
Revision as of 17:29, 21 August 2009
The best way people can help us out right now is by helping find the correct address we need to jump to in order to execute code. This has already been done on the 2G Nano and the 1G Classic. But now we really need help with the other iPods.
Matrix of working devices
This is a still incomplete matrix of working devices at the moment. It'll be updated and will at some time also include the actual address to jump in for each device.
| devices/partition type | Windows-formatted (FAT) | Mac-Formatted (HFS) |
|---|---|---|
| iPod nano 2g | Yes | Untested |
| iPod nano 3g | No | No |
| iPod nano 4g | crashed | No |
| iPod classic 1g | Yes | Untested |
| iPod classic 2g | No | No |
The staus "crashed" means that the device has crashed when putting in the modified notes but we couldn't find a address (yet) that is exploitable.
