Comment 10 for bug 192174

Danja,

Ok, I never noticed the stream mixing bug. Or, hm, maybe I did -- I think i
would get anomalous results every now and then. I didn't get a chance to
really evaluate your analysis on that.

And yes, I definitely like to pipe tcpflow to a binary decoder for doing
traffic analysis. I haven't heard of tcpxtract.

So I think we are definitely on the exact same page as to how we want
tcpflow to behave.

As far as starting from scratch, I mean starting from the latest tcpflow
upstream source, before applying Matteo's or anyone else's patch. If that
software contains your stream mixing bug, then obviously that will need to
be worked out in any case. I take it you don't see Matteo's patch as
introducing the stream mixing bug.

In any case, I don't think I can help much with the actual development. But
I can provide moral and technical support, as to demonstrating this is a
valid use case, and doing testing, etc.

- Rick

On Thu, Feb 25, 2010 at 12:24 PM, binary.koala <email address hidden>wrote:

> yes, i did look at your patch too, but i don't see how it would solve
> 'stream mixing' bug.
>
> i'm neither a C hacker, but desperately trying to marry tcpflow with
> foremost by using a pipe :)
> i did try tcpxtract, but it looks dated and suffers some problems of
> producing broken binaries.
>
> what do you mean by starting from scratch, new sets of patches or a
> completely new app?
>
> Danja
>
> --
> Allow binary dumping to stdout
> https://bugs.launchpad.net/bugs/192174
> You received this bug notification because you are a direct subscriber
> of the bug.
>