DontRespondTo setting no longer seems to work

Question

DontRespondTo setting no longer seems to work

cclements opened this issue 8 years ago · comments

In the latest build, Responder correctly lists the ip not to respond to when starting up, then responds and captures hashes anyway.

https://gist.github.com/cclements/afb260d4ad47a67745ac7be000e1f2a0

lgandx · Answer 1 · Wed Aug 17 2016 01:23:18 GMT+0800 (China Standard Time)

Thanks for your report. What's running on port 80?

Chris Clements · Answer 2 · Thu Aug 18 2016 12:16:48 GMT+0800 (China Standard Time)

Had an instance of darkhttpd running on the box I had forgotten about. Issue persists after killing it however.

lgandx · Answer 3 · Wed Aug 24 2016 08:10:33 GMT+0800 (China Standard Time)

Ok. Responder should never respond to its own IP address by default. The dontrespondto option is used for out of scope IP address or to avoid NAC detection.

lgandx · Answer 4 · Wed Sep 07 2016 02:27:18 GMT+0800 (China Standard Time)

This project has been forked the author. Issues/Feature requests/Pulls will only be supported by lgandx at this address: https://github.com/lgandx/Responder
If you have any suggestion, bugs, pulls, please use the new address.