| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <200311071628.hA7GS4e8020620@turing-police.cc.vt.edu> From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu) Subject: closing ports On Fri, 07 Nov 2003 15:30:56 +0200, hena <hena@...k.fi> said: > if your running linux try something like > iptables -t filter -A INPUT -p tcp -s 0.0.0.0 --syn -j REJECT > --reject-with tcp-reset that -s 0.0.0.0 won't do what you think. (It will drop all packets that have a source address of 0.0.0.0). I'd not bet on getting right results from '-s 0.0.0.0/0' either. You probably want to: a) Leave the -s 0.0.0.0 off entirely. b) Make this the *last* rule, and have other accepting rules before it. c) Include a ' -m limit --limit 4/sec -j LOG' rule or similar, so you know what it is you're dropping on the floor. d) Actually *LOOK AT* what (c) produces (yes, a daily summary via Perl script is OK). Many sites don't bother doing (d) and then get surprised when they get blindsided by something that the logs had given fair warning for.... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 226 bytes Desc: not available Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20031107/2ed9a5fb/attachment.bin
Powered by blists - more mailing lists