David Stainton

It was super easy to add this as an option here in my dev branch: https://github.com/david415/HoneyBadger/tree/64.afpacket_fanout_hash.0 The next step is to test this dev branch. I should probably ask people...

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.

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...

Dear @lattera I'm sorry I didn't see this sooner. For some reason I didn't receive the github notification for this ticket. Although I haven't lately been actively working on or...

@lattera honeybadger should build now. i fixed some bitrot and the unit tests. I think we should revive the packages. I managed to build honeybadger on freebsd; i built from...

looks good to me

ah yes that's an olde bug that sometimes shows up. i hope i get fix it soon. maybe later today... i don't have time right this minute.

i recently discovered that gopacket flows must be constructed using endpoints otherwise their String() method receiver breaks. ``` localIP, localPort, remoteIP, remotePort := t.getTCP4Tuple(t.conn) srcIPEndpoint := layers.NewIPEndpoint(localIP) dstIPEndpoint := layers.NewIPEndpoint(remoteIP)...

while adding a basic help2man man page i noticed the package build fails horribly, probably because an incorrect GOPATH where no dependencies are installed: ``` dh build --buildsystem=golang --with=golang dh_testdir...

so... if there were multiple applications that were relying on their own onion services via roflcoptor... and roflcoptor sees a connection close it should close it's control port destroying all...