Re: School project start: a fuzzer

[Arun Koshy <arunkoshy () gmail com>]

> documented, finished, presented. The question is, how deep can we go (what to
> promise in the specification)? My guess is that detecting success during
> fuzzing only when application crashes is too lame. "Feedback fuzzing" is maybe
> too complicated. What is realistic?

a couple of books on the topic that may be useful :

http://www.amazon.com/Fuzzing-Software-Security-Assurance-Information/dp/1596932147/ref=sr_1_1?ie=UTF8&s=books&qid=1241794318&sr=1-1

http://www.amazon.com/Gray-Hat-Python-Programming-Engineers/dp/1593271921

The authors ( or at least some of them ) hang out on d/d - so perhaps
you can expect responses from them as well ;)
_______________________________________________
Dailydave mailing list
Dailydave () lists immunitysec com
http://lists.immunitysec.com/mailman/listinfo/dailydave