Maximilian Lindner

Being able to run a sizer over multiple blocks would indeed be a nice feature. I'm not sure what problems we'll face implementing this. A simple for loop alone might...

I get your point. Do you have a practical example where such behavior would be beneficial? So far I've seen the previous messages as no more but preparations for the...

From the stacktrace it looks like you are using the callback_monitor? Here is what I think is happening: By increasing the amount of data in hashOfPswd, your target closes the...

Thanks for the report @Akim10150! I have just tested some very similar case on Linux where it works fine. That exception from your screenshot might be a bug in the...

Wouldn't setting a maximum for `num_sent` do the thing here? `sessions.py:` ```python def send(self, data): ... num_sent = self._target_connection.send(data=data) if self._fuzz_data_logger is not None: self._fuzz_data_logger.log_send(data[:num_sent]) ``` Or am I misunderstanding...

Shrinking the session class is definitely a good idea! It also seems reasonable to make this a breaking change. Keeping backwards compatibility will be a pain to implement I guess....

This works just fine for me. You could try to set a short `sleep_time` to prevent overloading your target or whatever else. ```python session = Session( target=Target( connection=SocketConnection("10.88.45.2", 80, proto='tcp')...

I had simmilar issues when fuzzing a http server on a different device. Whenever that device fully crashed or I pulled the network plug, boofuzz did too. In my case...

I'm currently working on a solution that keeps track of the last n test cases and only saves them to disk when a error or failure is logged. Saving the...

1. When you stop the test by SIGINT it will trigger log_error which will cause the db logger to save the last n test cases. Would that be sufficient? It...