> Suppose I was fuzzing a network application, which requires an entire session for a bug to be discovered I/O is a general problem for fuzzing and IMO the si

> Suppose I was fuzzing a network application, which requires an entire session for a bug to be discovered I/O is a general problem for fuzzing and IMO the simplest/most general approach is to try and decompose the code under test to find a part that is able to accept a single input stream. EDIT: e.g. for an SSL/TLS library -- if you had a bool msg_create(msg_t *msg, void *input, size_t len_bytes) function, you could fuzz that one easily.