Timeline for Fuzzing Android API
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 15, 2012 at 14:01 | answer | added | Lucas Kauffman | timeline score: 1 | |
| Jul 26, 2012 at 12:05 | comment | added | Polynomial | Yes, that's a viable solution. However, you're still going to need to capture the fault and dig through for info. I'm not telling you not to try it, I'm just saying it might be a good idea to try something local (e.g. Windows / Linux) first. | |
| Jul 26, 2012 at 12:01 | comment | added | tkit | @Polynomial - would it be plausible to create a fuzzer as an android app, and monitor the output of fuzzing through adb->logcat (android debug bridge (shell))? I thought that would give me the right kind of access to what the fuzzer would output. | |
| Jul 26, 2012 at 11:53 | comment | added | Polynomial | I'd suggest playing around with something a little more accessible first. An Android fuzzer requires you to write a lot of code that talks to the target device, which makes the process quite a bit more complex. | |
| Jul 26, 2012 at 10:30 | history | asked | tkit | CC BY-SA 3.0 |