#137 inject.after-packet is not implemented properly

Open
opened 6 years ago by jens.klein · 0 comments

This leads to inject.after-packet being available for nearly every attack, but never used within these attacks.

Implementing it requires a timestamp extraction for individual packets, which are not and can not be stored in the database due to the amount of data it is. So an efficient way to go through all packets in a pcap is needed to get the required timestamp and set it as inject.at-timestamp parameter.

This leads to inject.after-packet being available for nearly every attack, but never used within these attacks. Implementing it requires a timestamp extraction for individual packets, which are not and can not be stored in the database due to the amount of data it is. So an efficient way to go through all packets in a pcap is needed to get the required timestamp and set it as inject.at-timestamp parameter.
Sign in to join this conversation.
No Milestone
No assignee
1 Participants
Loading...
Cancel
Save
There is no content yet.