Timeout for fuzzers defaults to 0

Question

Timeout for fuzzers defaults to 0

neuromancer opened this issue 5 years ago · 4 comments

https://github.com/trailofbits/deepstate/blob/master/bin/deepstate/core/fuzz.py#L124

Answer 1 · 2019-12-27T21:06:17.000Z

Hmm, looks simple to fix; should be 3600 @ex0dus-0x right? Doesn't look like most executors override....

Answer 2 · 2019-12-28T01:54:10.000Z

Use here was done in order to signify that if self.timeout is set to a default 0, there would be no timeout enforced and the process would run indefinitely. Found that running executors on a container worker with a finite implicit timeout led to it dying before exploring all paths, and may not be ideal when we might continuously run an executor to maximize crashes to be found.

Answer 3 · 2019-12-28T02:18:34.000Z

I tested it with eclipser and it stops as soon as the tool starts (so it is very confusing from the user perspective).

Answer 4 · 2019-12-28T03:04:21.000Z

Yeah, I am pretty sure this needs overridden for sensible Eclipser behavior.