Suricata

Related to #1017

First step would be to document the chunks of file(s) as identified per sensor, if multiple sensors are in use.

My understanding is the following :
We now log the byte-range but we would like suricata to handle the complete file reassembly (in case there is any).
Is that correct ?
Is there already an example of suricata of reassembly over TCP ? And in this case over different flows ?

We will split those in multiple smaller tasks.

First is rebuilding the file if multiple requests/responses are in the same flow

Does anyone remember WHAT smaller tasks we wanted to create :)?

First is rebuilding file if multiple transactions are in the same flow (maybe first subclass, if they are in the right order)
Then next task would be to see what to do if the transactions are across many flows

So, we would like :

• This container can be generic with a key, and a type for the key
  - To handle unordered ranges
• That means storing an unordered range up until we can do the reassembly
• We need to limit the memory consumption... use a global memcap for these containers ?
• We also need timeouts (the new container shall timeout as flow time out)