full-disclosure - ICMP (was: daily internet traffic report)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: blancher at cartel-securite.fr (Cedric Blancher)
Subject: ICMP (was: daily internet traffic report)

Le dim 17/10/2004 ? 22:21, James Edwards a ?crit :
> So, blocking ***all*** ICMP ***types*** is bad but you can block some
> ***types*** without getting into trouble. Till you understand that all
> the types do in relation to networking I would leave the alone.

Nowadays, using a decent stateful firewall allows one to get rid of ICMP
filtering by associating ICMP errors to existing connections. As an
example, when filtering using Netfilter, ICMP errors triggered by known
IP connections are recognized as such (i.e. RELATED state) and thus can
be filtered in a different way unsollicited ones (i.e. INVALID state)
are.

This kind of feature allows one not to block valid ICMP stuff and keep
away from direct ICMP solicitations you can filter the way you want.

My 0.02?...

-- 
http://www.netexit.com/~sid/
PGP KeyID: 157E98EE FingerPrint: FA62226DA9E72FA8AECAA240008B480E157E98EE
>> Hi! I'm your friendly neighbourhood signature virus.
>> Copy me to your signature file and help me spread!