Antti Vähä-Sipilä
Antti Vähä-Sipilä
Apparently the tool I mentioned above is not complete.
Actually I just today thought about this and probably I'm going to create some sort of class that wraps the tools and their configuration, and modify the currently existing Behave...
Here's a bit more background for getting rid of Behave. The tool is supposed to be used in a system where, when new APIs are added, injection and fuzz tests...
Re packaging, I am mainly just worried about maintaining the directory hierarchy because I know some projects clone the repo and assume stuff is where it is now; and on...
Using Zap would be a great idea, but I think the more pressing issue is Bug #15. Myself, I do not have immediate need to support Zap, so if anyone...
Database schema extensions and all the database plumbing has been implemented as a part of #11.
Walking through one integration example with Jenkins would probably be a good idea. I am opening this ticket and will attend to this if I have the time in the...
Tested Sony Xperia Pro (MK16i) running ICS 4.0.4, with an OTG cable that is known good (used with other software on that specific device). I know this is an old...
Ok, the problem might be in these kernel messages that are seen when plugging in. Hypothesis: Not able to supply enough power and it fails later due to that. What...
The current design of the fuzzer just sends packets without regard to any state machine. Authentication mechanisms that require state at the fuzz tool end, or that require cryptographic algorithms...