lgandx / Responder

Responder is a LLMNR, NBT-NS and MDNS poisoner, with built-in HTTP/SMB/MSSQL/FTP/LDAP rogue authentication server supporting NTLMv1/NTLMv2/LMv2, Extended Security NTLMSSP and Basic HTTP authentication.
GNU General Public License v3.0
5.47k stars 776 forks source link

Error return when run responder.py #230

Closed secfung closed 1 year ago

secfung commented 1 year ago

Hi All,

I got this error when running responder.py on kail linux. Any clue for this issue? thank you!

responder -I eth0 -A

Traceback (most recent call last): File "/usr/lib/python3.10/configparser.py", line 790, in get value = d[option] File "/usr/lib/python3.10/collections/init.py", line 986, in getitem return self.missing(key) # support subclasses that define missing File "/usr/lib/python3.10/collections/init.py", line 978, in missing raise KeyError(key) KeyError: 'dcerpc'

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/usr/share/responder/./Responder.py", line 58, in settings.Config.populate(options) File "/usr/share/responder/settings.py", line 99, in populate self.DCERPC_On_Off = self.toBool(config.get('Responder Core', 'DCERPC')) File "/usr/lib/python3.10/configparser.py", line 793, in get raise NoOptionError(option, section) configparser.NoOptionError: No option 'dcerpc' in section: 'Responder Core'

also-here commented 1 year ago

Hi secfung,

I'm pretty sure the issues is/was that you are using an older Responder.conf file (referenced as 'Responder Core' in your error message). Essentially, lgandx has kindly added some fun new servers, e.g. DCERPC, WINRM, SNMP, and Responder.py is checking Responder.conf to see if they should be on or off. When it doesn't find them listed you get that error message. You can either grab a fresh copy of Responder.conf from here or, if you've hacked up your local copy and want to keep it, you can just add the missing options to the list of servers. If you are missing DCERPC you're likely missing others so make sure they're all there or we'll be right back here dealing with a slightly updated error message.

TL;DR It's cuz of the Responder.conf file. Pull a new copy.

secfung commented 1 year ago

Thanks and the problem is fixed.

On Wed, 15 Mar 2023 at 10:55, also-here @.***> wrote:

Hi secfung,

I'm pretty sure the issues is/was that you are using an older Responder.conf file (referenced as 'Responder Core' in your error message). Essentially, lgandx has kindly added some fun new servers, e.g. DCERPC, WINRM, SNMP, and Responder.py is checking Responder.conf to see if they should be on or off. When it doesn't find them listed you get that error message. You can either grab a fresh copy of Responder.conf from here or, if you've hacked up your local copy and want to keep it, you can just add the missing options to the list of servers. If you are missing DCERPC you're likely missing others so make sure they're all there or we'll be right back here dealing with a slightly updated error message.

TL;DR It's cuz of the Responder.conf file. Pull a new copy.

— Reply to this email directly, view it on GitHub https://github.com/lgandx/Responder/issues/230#issuecomment-1469232732, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT6XADU3VZKF5NWM743WLDLW4EVSFANCNFSM6AAAAAAVJPXH4M . You are receiving this because you authored the thread.Message ID: @.***>