You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
When being port-scanned, it would be nice to know who is scanning us.
Maybe this info can be parsed from lsof? It's a bit difficult since portscans are very rapid and usually rely on collecting port-closed RST responses, and not opening TCP sockets for very long.
The text was updated successfully, but these errors were encountered:
Not to mention the source IP info is not available directly from the logfile, so we'd have to run an additional command to try and figure out the source.
When being port-scanned, it would be nice to know who is scanning us.
Maybe this info can be parsed from
lsof
? It's a bit difficult since portscans are very rapid and usually rely on collecting port-closed RST responses, and not opening TCP sockets for very long.The text was updated successfully, but these errors were encountered: