#137 inject.after-packet is not implemented properly

開啟中
jens.klein6 年之前創建 · 0 條評論

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.
登入 才能加入這對話。
未選擇標籤
Bug
未選擇里程碑
未指派成員
1 參與者
正在加載...
取消
保存
尚未有任何內容