View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002251Kali LinuxKali Package Bugpublic2015-05-01 01:232016-12-05 19:09
ReporterLeeRock Assigned Tomuts  
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product Version1.1.0 
Summary0002251: Responder - Error starting TCP server on port 443
Description

root@kali:~# responder -i 172.18.233.45 -I eth0 -wrf
NBT Name Service/LLMNR Responder 2.0.
Please send bugs/comments to: [email protected]
To kill this script hit CRTL-C

[+]NBT-NS, LLMNR & MDNS responder started
[+]Loading Responder.conf File..
Global Parameters set:
Responder is bound to this interface: eth0
Challenge set: 1122334455667788
WPAD Proxy Server: True
WPAD script loaded: function FindProxyForURL(url, host){if ((host == "localhost") || shExpMatch(host, "localhost.") ||(host == "127.0.0.1") || isPlainHostName(host)) return "DIRECT"; if (dnsDomainIs(host, "RespProxySrv")||shExpMatch(host, "(.RespProxySrv|RespProxySrv)")) return "DIRECT"; return 'PROXY ISAProxySrv:3141; DIRECT';}
HTTP Server: ON
HTTPS Server: ON
SMB Server: ON
SMB LM support: False
Kerberos Server: ON
SQL Server: ON
FTP Server: ON
IMAP Server: ON
POP3 Server: ON
SMTP Server: ON
DNS Server: ON
LDAP Server: ON
FingerPrint hosts: True
Serving Executable via HTTP&WPAD: OFF
Always Serving a Specific File via HTTP&WPAD: OFF

Error starting TCP server on port 443. Check that you have the necessary permissions (i.e. root), no other servers are running and the correct network interface is set in Responder.conf.

Steps To Reproduce

I validated that nothing was running on 443.
root@kali:~# netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:5984 0.0.0.0:* LISTEN 24441/beam.smp

Additional Information

I opened a ticket on the Responder github and received that following:

From: lgandx
If nothing is listening on 443, it must be an implementation issue. Please check with Kali Team.

Activities

muts

muts

2015-05-01 06:49

reporter   ~0003268

Last edited: 2015-05-01 07:00

Confirmed, however there's nothing for us to implement differently in our packaging.
muts

muts

2015-05-01 07:07

reporter   ~0003269

My mistake, looks like the Certs directory wasn't copied over.
muts

muts

2015-05-01 07:13

reporter   ~0003270

Fix (and update) pushed, should hit the main repos within the hour.

Issue History

Date Modified Username Field Change
2015-05-01 01:23 LeeRock New Issue
2015-05-01 06:49 muts Note Added: 0003268
2015-05-01 06:50 muts Note Edited: 0003268
2015-05-01 07:00 muts Note Edited: 0003268
2015-05-01 07:07 muts Note Added: 0003269
2015-05-01 07:13 muts Note Added: 0003270
2015-05-01 07:13 muts Status new => closed
2015-05-01 07:13 muts Assigned To => muts
2015-05-01 07:13 muts Resolution open => fixed
2015-05-01 07:13 muts Fixed in Version => 1.1.1
2015-05-01 07:14 muts Status closed => resolved