search

infobyte / spoilerwall

Spoilerwall introduces a brand new concept in the field of network hardening. Avoid being scanned by spoiling movies on all your ports!
GNU General Public License v3.0
761 stars 42 forks source link

Determine scanned-for port from client... #12

Open infracritical opened 7 years ago

infracritical commented 7 years ago

This might take a while to explain, but I will do my best.

When I conduct a port scan using 'nmap', I would like to know the port that it is trying to connect to. So, in this case, port 23 (telnet). Once port 23 is connected by 'nmap', I'd like to know on the server side that port 23 was just scanned from the client.

I don't profess to know Python (am a newbie when it comes to this object-oriented language), but so far, have had little to no luck, as Python doesn't seem to offer you more granular features when it comes to socketed connections.

Additionally, since port 8080 is acting as the proxy-forwarder, how can I ensure that I report back that it's port 23...and NOT port 8080?

infracritical commented 7 years ago

Wanted to provide a graphical representation of what I think is the process. Essentially, 'iptables' is what's performing all of the heavy lifting, right?

image

Ezequieltbh commented 7 years ago

Hi @infracritical ! If you want know the original port scanned by tools like Nmap, you can use the iptables logging for that. Due to forwarding you cant use python server for that. Here you can read more about that logging feature!

https://websistent.com/linux-iptables-log-everything/