Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

detect FIN and RST injection #83

Open
david415 opened this issue Feb 12, 2016 · 2 comments
Open

detect FIN and RST injection #83

david415 opened this issue Feb 12, 2016 · 2 comments

Comments

@david415
Copy link
Owner

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

@david415
Copy link
Owner Author

Perhaps we should first remove the broken FIN+RST injection detection?

We can only claim to detect the protocol anomalies we test for in unit tests and pcap integration tests.

@david415
Copy link
Owner Author

for the record we have working censorship-injection detection in this dev branch:
https://github.com/david415/HoneyBadger/tree/detect-censor-injection.2

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant