Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: LinuxMint, Ubuntu Server, RHEL7 (in the past: Ubunu, Debian, Suse, Fedora, RedHat)
Posts: 29
Rep:
Anti-port sanning
Is there a way to stop some to scan my computer for opened ports? Someone i know did something so i taks about a min to scan (the one who scans gets bored)
Any ideeas?
the usual (read : nmap) scanners usually use SYN tcp flag to know if a port is open or not. So limiting the number of syn flag you allow would really slow down a scanning ( it could maybe even make it hang I believe). So setting a limit rules about SYN flag would be an idea.
HOWEVER, be aware this might be used against you, someone knowing the tricks could just send you endless stream of SYN to make your computer stop responding to connection (basic DDOS). If you plan to use this, make sure to place this carefully in your firewall, make sure any critical service ACCEPT communication before the limit rule is checked.
Ps : if you just want port to appears as CLOSED instead of firewalled, you could use "-j REJECT --reject-with tcp-reset" instead of DROP. This often confuse ports scanners.
if you change you iptables default policy to drop it will take forever to scan you completely, although it does'nt stop it. And don't blacklist people for scanning you because the source address can be spoofed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.