You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've had some broken logic in the source tree which probably never really worked for detecting RST and FIN injection. There's lots of good papers on the subject... so we can at least implement some basic RST and FIN injection.
To implement this I'll be experimenting with using the Block API to express a zero-length overlap... and additionally we can check TCP flags for FIN and RST. Not sure if this creates false positives and additional injection detection heuristics are needed perhaps.
We should not only write proper unit tests for this feature but also we need to generate new pcap files and add them to the pcap git repo so that they become part of the reproducible pcap-driven integration test suite ;-p
The text was updated successfully, but these errors were encountered:
however it seems to produce lots of false positives since the criteria for detection is apparently caused by normal TCP behavior... or what do people think of this dev branch?
We've had some broken logic in the source tree which probably never really worked for detecting RST and FIN injection. There's lots of good papers on the subject... so we can at least implement some basic RST and FIN injection.
To implement this I'll be experimenting with using the Block API to express a zero-length overlap... and additionally we can check TCP flags for FIN and RST. Not sure if this creates false positives and additional injection detection heuristics are needed perhaps.
We should not only write proper unit tests for this feature but also we need to generate new pcap files and add them to the pcap git repo so that they become part of the reproducible pcap-driven integration test suite ;-p
The text was updated successfully, but these errors were encountered: