full-disclosure - Learn from history?

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>] [day] [month] [year] [list]

Message-ID: <D54AB2ADB72C164B8251422DE1D3234222AD07@srv900045>
From: svgn at orbid.be (Serge van Ginderachter (svgn))
Subject: Learn from history?

> If wormX propogates using port Y, block any traffic with 
> source/destination port Y.  

Exactly. Note that those ports probably should have been blocked already.
Hen they are open, they should be open for servers/services that REALLY
needed them only and only if it's safe to do it.

Now that might probably have been the case on the border, but not on the
local LAN... (which was my initial intended remark)

> It doesn't solve the problem, it slows the spreading. If you
> get infected, we don't need to you spread it further.  Block the shit
> from going outbound.  

Totally agree, but IRL...
do you have any idea how much small businesses have just a NAT router
instead of a real firewall?

Serge