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

Responder with fingerprinting goes undetected #6

Open
kirillwow opened this issue Mar 13, 2018 · 2 comments
Open

Responder with fingerprinting goes undetected #6

kirillwow opened this issue Mar 13, 2018 · 2 comments

Comments

@kirillwow
Copy link

Responder probes querying machine and doesnt spoof if get no answer back. Probably listening to 445/TCP may help.
image

@n00py
Copy link

n00py commented May 1, 2020

I just attempted this with Responder -f, and it does send the LLMNR response. The SMB request for fingerprinting does not happen until after the LLMNR response. Respounder just detects that LLMR spoofing is taking place, not sure what SMB would add in this case.

@codeexpress
Copy link
Owner

codeexpress commented May 1, 2020

This is true. The goal here is to detect the presence of responder running in a network by sending a fake LLMNR request and force responder to respond to that.

This is what respounder does for now. The only case when adding SMB support will be useful is when someone is running responder to respond to SMB but not to LLMNR. In its default setting this is not the case and hence this tool will catch most instances.

Adding SMB will mean that the respounder should also add support for each protocol that responder supports, which seems a lot of additional work for a very little gain.

Makes sense?

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

No branches or pull requests

3 participants