-
I'm fuzzing a service that communicates over two TCP ports - one for requests and one for responses. For example, I send a request to TCP 999 and would receive its respective response over TCP 1999 (TCP 999 returns nothing). Is there an elegant way boofuzz can take this communication use-case into account in order to avoid aborting fuzzing? Please let me know at your earliest convenience. Thanks in advance! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
In order to simply avoid failing, you could set However, to actually receive the data over the second port and do something with it would be different. There is nothing like this built in, but you might be able to get by using (overriding) the If you try this out, let us know how it goes! |
Beta Was this translation helpful? Give feedback.
-
I'm sure there's a better way to do this but here's what I came up with:
|
Beta Was this translation helpful? Give feedback.
-
Thanks for sharing your solution @ninp0! |
Beta Was this translation helpful? Give feedback.
I'm sure there's a better way to do this but here's what I came up with: