full-disclosure - SQL Slammer

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]

Message-ID: <3E46D50F.6050405@guninski.com>
From: guninski at guninski.com (Georgi Guninski)
Subject: SQL Slammer - lessons learned

Schmehl, Paul L wrote:
..snip...
> Are you really willing to demand your "freedom" in the face of the
> overwhelming odds that leaving those ports open will do more harm than
> good?
> 

I am willing to demand my freedom.
When I pay to an ISP for internet, I want to have all ports in/out working.
If I don't want something working, I filter it at *my* firewall.

When code red/nimbda hit some time ago on port 80, nobody suggested blocking 
port 80 for those II$, right? But when a worm hits on less popular port, people 
start attacking the symptoms, not the cause. Am I missing something?

Georgi Guninski
http://www.guninski.com